CVE-2026-88920, CVE-2026-85532, CVE-2026-92899

Data: 2026-10-03

Severity: Critical

CVSS Score:

• CVE-2026-88920: 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)

• CVE-2026-85532: 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H)

• CVE-2026-92899: 4.8 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N)

Riferimenti:

• CVE-2026-88920:

  • https://nvd.nist.gov/vuln/detail/CVE-2026-88920

  • https://lists.apache.org/thread/grt43m3bgbzz0mk0cnho3rcybb1j01z9

  • https://www.openwall.com/lists/oss-security/2026/09/30/10

• CVE-2026-85532:

  • https://nvd.nist.gov/vuln/detail/CVE-2026-85532

  • https://lists.apache.org/thread/7jllcpbf4nbzhdp2vchz5yplnl5w6vd6

  • https://www.openwall.com/lists/oss-security/2026/09/30/8

• CVE-2026-92899:

  • https://nvd.nist.gov/vuln/detail/CVE-2026-92899

  • https://lists.apache.org/thread/nrzngsz1xm2lztq3t873663xx9wnrwm7

  • https://www.openwall.com/lists/oss-security/2026/09/30/13

Libreria: org.apache.wss4j:*

• GovWay 3.3.x: <= 2.4.3

• GovWay 3.4.x: <= 4.0.1

Descrizione

1. [CVE-2026-88920] CWE-287: Improper Authentication

An authentication bypass in the DOM security processor in Apache WSS4J allows unauthenticated remote attackers to forge authenticated SOAP messages via a crafted unsigned SAML sender-vouches assertion containing an attacker-controlled key.

Users are recommended to upgrade to versions 4.0.2 or 3.0.6 or 2.4.4, which fix this issue.

2. [CVE-2026-85532] CWE-20: Improper Input Validation

Apache WSS4J accepted attacker-controlled derived-key lengths and offsets without adequate bounds. This could permit cryptographically weak keys or excessive CPU and memory consumption when processing crafted WS-Security messages. The fixes enforce a minimum key length of 16 bytes, a maximum length of 512 bytes, and a maximum offset of 4096 bytes. Users are recommended to upgrade to versions 4.0.2 or 3.0.6 or 2.4.4, which fix this issue.

3. [CVE-2026-92899] CWE-290: Authentication Bypass by Spoofing

Apache WSS4J remembers the Nonce of each UsernameToken it accepts, so a captured token cannot be reused. It stored the Nonce as raw base64 text, but authentication decodes that text and uses the bytes.The same bytes can be written as base64 in several ways. An attacker who captured an authenticated request could re-send it with a space added to the Nonce: the password digest still verified, but the token no longer matched the remembered one, so the replay was accepted. Since a UsernameToken does not cover the message body, the captured token could then be reused on requests of the attacker’s choosing until it expired. Affects deployments with a nonce replay cache configured, as Apache CXF has by default, and only tokens using a password digest. The cache is now keyed on the decoded Nonce. Users are recommended to upgrade to versions 4.0.2 or 3.0.6 or 2.4.4, which fix this issue.

GovWay

Versione affette:

• 3.3.x: <= 3.3.20

• 3.4.x: <= 3.4.3

Risoluzione:

• 3.3.x: 3.3.21

• 3.4.x: 3.4.4