Skip to main content
Menu
CVEs

CVE

org/apache:wss4j:wss4j-ws-security-common replay protection bypass in WS-Security message handling

CVE-2026-115690EUVD-2026-126194GHSA-CV54-5MP3-5JF6

Exploited
No known exploitation
Fix
Fixed in 4.0.3, 3.0.7, 2.4.5
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 4.0.3, 3.0.7, 2.4.5.

Published
Last modified
Reference
Last checked
0.15% · 3rd percentile
10/100 · provisional
None on Exploit-DB, Metasploit or GitHub

Summary

Apache WSS4J, the Apache Software Foundation library for WS-Security message handling, can accept the same captured message more than once when several copies arrive at the same time, because its replay check and its recording of the message happen in separate steps. An attacker who obtains a valid message while it is still in transit could use this to repeat the same authenticated request.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Original 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.

cve.now Index

10Pcve.now Index 10 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach10/20Affects Maven packages
  • Severity?/10Unknown. No CVSS score or vendor rating
  • No patch0/5No signal

What would change the score

  • Would score about 65 if added to CISA KEV
  • Would score about 60 if CISA's SSVC rates exploitation active
  • Would score about 32 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 4.0.3, 3.0.7, 2.4.5.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-115690 (Apache WSS4J: Replay protection bypassed by concurrent copies of a message), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-115690 (entry last updated 2026-11-16):
Affected:
- Maven package org/apache:wss4j:wss4j-ws-security-common: from 4.0.0, fixed in 4.0.3; from 3.0.0, fixed in 3.0.7; fixed in 2.4.5
Fixed versions: 4.0.3, 3.0.7, 2.4.5.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-115690 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-115690 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (Maven): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://lists.apache.org/thread.html/y2gb5of7tbh08zqv8rlh8212720f6tcy
- http://www.openwall.com/lists/oss-security/2026/11/16/4
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-115690
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-115690"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Record last updated

Affected versions

Evidence 4

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Write-ups · 1

Establishes: Technical detail and context.

  1. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-115690

Is CVE-2026-115690 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-115690?

org/apache:wss4j:wss4j-ws-security-common (Maven): from 4.0.0 before 4.0.3; from 3.0.0 before 3.0.7; before 2.4.5.Source: cve.now feed data

How do I fix CVE-2026-115690?

Upgrade to a fixed version: 4.0.3, 3.0.7, 2.4.5.Source: cve.now feed data