CVE-2026-115690
Last modified
CVE-2026-115690 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.15% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Apache Software Foundation | Apache WSS4J | >= 4.0.0, < 4.0.3; >= 3.0.0, < 3.0.7; < 2.4.5 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-115690?
How severe is CVE-2026-115690?
How do I fix CVE-2026-115690?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-115678Arm Keil MDK-Middleware 8.0.0-8.3.0 may allow pre-authentica…5.3
- CVE-2026-115679Arm Keil MDK-Middleware 8.3.0 may allow out-of-bounds reads …6.5
- CVE-2026-11568The Product Configurator for WooCommerce WordPress plugin be…7.5
- CVE-2026-115680Arm Keil MDK-Middleware 8.0.0-8.3.0 may allow DHCPv6 Option-…6.5
- CVE-2026-115683A race condition in Epiphany allows a malicious website to b…6.8
- CVE-2026-11569A flaw was found in Quay. The filedrop endpoint accepts any …5.4
- CVE-2026-115693Improper Certificate Validation vulnerability in hackney_ssl…9.1
- CVE-2026-1157A vulnerability was identified in Totolink LR350 9.3.5u.6369…8.8
- CVE-2026-11570The User Submitted Posts WordPress plugin before 20260608 d…4.2
- CVE-2026-115700Interpretation Conflict vulnerability in hackney_url in beno…6.9
- CVE-2026-115701Allocation of Resources Without Limits or Throttling vulnera…8.2
- CVE-2026-115706Authorization Bypass Through User-Controlled Key (CWE-639) i…6.8
Are you affected by CVE-2026-115690?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
