---
id: "CVE-2026-115690"
page: "https://infrastack.ai/live/CVE-2026-115690"
kind: "vulnerability"
aliases: ["CVE-2026-115690"]
title: "Apache WSS4J: race lets captured SOAP messages be replayed multiple times"
severity: "medium"
cvss: null
epss: 0.00147
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["apache-cxf", "java", "package", "soap", "web-services", "wss4j"]
not_affected_if: ["message-already-processed", "no-replay-cache", "tls-protected-transport"]
published_at: "2026-11-16T10:16:45+00:00"
first_seen_at: "2026-11-16T10:39:25+00:00"
updated_at: "2026-11-16T18:53:18+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-115690", "first_seen_at": "2026-11-16T10:39:25+00:00"}, {"source": "epss", "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-115690", "first_seen_at": "2026-11-16T18:53:18+00:00"}]
exploit_sources: [{"type": "epss", "score": 0.00147, "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-115690"}]
---

# Apache WSS4J: race lets captured SOAP messages be replayed multiple times

Link for people: https://infrastack.ai/live/CVE-2026-115690 (this .md is for agents)

Apache WSS4J checked whether a message nonce, timestamp, signature or SAML OneTimeUse ID was already seen and remembered it in two separate steps, so concurrent copies of one message could all pass. An attacker who captures a message in transit can make the same authenticated request run more than once.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the WSS4J version in the project's dependency file or `mvn dependency:tree` output, looking for `wss4j-ws-security-dom` or `wss4j-ws-security-common`.
- Check whether a replay cache is configured (Apache CXF enables one by default) and whether a custom `ReplayCache` implementation is in use.

## Fix

- Upgrade to `4.0.3`, `3.0.7` or `2.4.5`, which fix this issue.
- Custom `ReplayCache` implementations should override the new `ReplayCache.addIfAbsent` method with an operation that is atomic in their underlying store.

## Timeline

- 2026-11-16T10:39:25+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-115690
- 2026-11-16T18:53:18+00:00 epss https://api.first.org/data/v1/epss?cve=CVE-2026-115690

## From the sources

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.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_
