Skip to content
VulniPulse
High7.5Apache Software Foundation Updated

CVE-2026-115690: Apache CXF: Apache WSS4J remembers the UsernameToken Nonce, the Timestamp and signature of a signed message, and the ID of a SAML 2.0 "OneTimeUse" assertion, so that a captured message cannot be accepted twice

This Apache advisory covers CVE-2026-115690 in Apache CXF.

Open the Apache advisory

Key facts

Vendor rating
High, CVSS 7.5
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N · base score 7.5, scored by CISA-ADPAttack vector: network. Attack complexity: low. Privileges required: none. User interaction: none. Scope: unchanged. Confidentiality impact: none. Integrity impact: high. Availability impact: none.
Weakness
  • CWE-367 Time-of-check time-of-use (TOCTOU) race condition
EPSS
0.27% chance of exploitation in the next 30 days (19th percentile). FIRST EPSS, .
CISA SSVC
Exploitation: none observed. Automatable: yes. Technical impact: partial. CISA, .
CISA KEV
Not listed (catalogue checked )
Affected
Apache WSS4J 4.0.0 before 4.0.3; Apache WSS4J 3.0.0 before 3.0.7; Apache WSS4J before 2.4.5
Fixed in
4.0.3, 3.0.7, 2.4.5
Source published
Source revised
Listed by VulniPulse
Record changed

Compiled by VulniPulse from the linked sources. How records are collected and checked.

Affected products & platforms

Apache Software FoundationApache CXF

Description

Apache WSS4J remembers the UsernameToken Nonce, the Timestamp and signature of a signed message, and the ID of a SAML 2.0 "OneTimeUse" assertion, so that a captured message cannot be accepted twice. It checked whether a value had already been seen, validated the message, and only then remembered the value, as two separate steps.

If several copies of the same message were processed at the same time, they could all pass the check before any of them was remembered, and all be accepted. An attacker who obtained a valid message before the recipient first processed it could send several copies at once, so that the same authenticated request was executed more than once.

Where a UsernameToken is not bound to the message by a signature, the copies could carry different message bodies. The attacker needs to obtain the message while it is still in transit; a message captured after it has been accepted cannot be replayed.

Affects deployments with a replay cache configured, as Apache CXF has by default. The value is now checked and remembered in a single atomic step.

Custom ReplayCache implementations should override the new ReplayCache.addIfAbsent method with an operation that is atomic in their underlying store. Users are recommended to upgrade to versions 4.0.3 or 3.0.7 or 2.4.5, which fix this issue.

Text from the source record.

Affected versions
  • Apache WSS4J 4.0.0 before 4.0.3
  • Apache WSS4J 3.0.0 before 3.0.7
  • Apache WSS4J before 2.4.5

Official advisory · high-confidence parse· fetched ·verify at source

How to fix CVE-2026-115690

Upgrade to the first fixed release for your version, shown in the table above.

Vendor guidance

  • Users are recommended to upgrade to versions 4.0.3 or 3.0.7 or 2.4.5, which fix this issue.

Apache Software Foundation advisories, November 2026All Apache Software Foundation advisories

Get an email when Apache publishes the next one.

See Apache's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.

Alert me about Apache