Skip to main content
No exploitation reportedAwaiting NVD analysis

CVE-2026-115690

Apache WSS4J: Replay protection bypassed by concurrent copies of a message

No exploitation reported by the sources we read.

  • Published2026-11-16
  • WeaknessCWE-367

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2026-11-1609:54CVE publishedCNA

Versions per branch

Products declared by the CNA1 product

As apache, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • Apache Software Foundation Apache WSS4Jother versions: not affected

    package org/apache:wss4j:wss4j-ws-security-commonhttps://repo.maven.apache.org/maven2

    Affected
    • ≥ 4.0.0, < 4.0.3fixed in 4.0.3semver
    • ≥ 3.0.0, < 3.0.7fixed in 3.0.7semver
    • < 2.4.5fixed in 2.4.5semver

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-11-16

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • wss4jUbuntu:26.10all versions · no fixed version listed
  • wss4jUbuntu:26.04:LTSall versions · no fixed version listed
  • wss4jUbuntu:24.04:LTSall versions · no fixed version listed
  • wss4jUbuntu:22.04:LTSall versions · no fixed version listed
  • wss4jUbuntu:20.04:LTSall versions · no fixed version listed
  • wss4jUbuntu:18.04:LTSall versions · no fixed version listed
  • wss4jUbuntu:16.04:LTSall versions · no fixed version listed

Full record on NVD

Fix

No fix published by the sources we read yet. NVD record

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Published
2026-11-16
Last Modified
2026-11-17
NVD status
Received
GitHub Advisory
GHSA-cv54-5mp3-5jf6

Frequently asked questions

What is CVE-2026-115690?

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.

Is CVE-2026-115690 actively exploited?

Active exploitation of CVE-2026-115690 has not been confirmed. Its EPSS score was 0.1% on 2026-11-16, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-115690?

CVE-2026-115690 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N.

Running wss4j? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record