UBUNTU-CVE-2026-115690 (CVE-2026-115690)
Vulnerability from osv_ubuntu – Published: 2026-11-16 00:00 – Updated: 2026-11-16 00:00 – Source websiteApache 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.
{
"affected": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libwss4j-java",
"binary_version": "1.6.15-2"
}
]
},
"package": {
"ecosystem": "Ubuntu:16.04:LTS",
"name": "wss4j",
"purl": "pkg:deb/ubuntu/wss4j@1.6.15-2?arch=source\u0026distro=xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.6.15-2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libwss4j-java",
"binary_version": "1.6.19-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "wss4j",
"purl": "pkg:deb/ubuntu/wss4j@1.6.19-1?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.6.19-1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libwss4j-java",
"binary_version": "1.6.19-2"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "wss4j",
"purl": "pkg:deb/ubuntu/wss4j@1.6.19-2?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.6.19-2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libwss4j-java",
"binary_version": "1.6.19-2"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "wss4j",
"purl": "pkg:deb/ubuntu/wss4j@1.6.19-2?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.6.19-2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libwss4j-java",
"binary_version": "1.6.19-3"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "wss4j",
"purl": "pkg:deb/ubuntu/wss4j@1.6.19-3?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.6.19-3"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libwss4j-java",
"binary_version": "1.6.19-4build1"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.10",
"name": "wss4j",
"purl": "pkg:deb/ubuntu/wss4j@1.6.19-4build1?arch=source\u0026distro=stonking"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.6.19-4build1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libwss4j-java",
"binary_version": "1.6.19-4build1"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.04:LTS",
"name": "wss4j",
"purl": "pkg:deb/ubuntu/wss4j@1.6.19-4build1?arch=source\u0026distro=resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.6.19-4",
"1.6.19-4build1"
]
}
],
"aliases": [],
"details": "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.",
"id": "UBUNTU-CVE-2026-115690",
"modified": "2026-11-16T00:00:00Z",
"published": "2026-11-16T00:00:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2026-115690"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-115690"
},
{
"type": "REPORT",
"url": "https://lists.apache.org/thread.html/y2gb5of7tbh08zqv8rlh8212720f6tcy"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2026-115690"
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.