CVE-2026-115690
org/apache:wss4j:wss4j-ws-security-common replay protection bypass in WS-Security message handling
An attacker holding a valid message in transit can send simultaneous copies to repeat an authenticated request.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Fuente: CISA-ADP
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | CVE-2026-115690 divulgada · CVSS 7.5 (CISA-ADP) | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Fuente: NIST NVD | Registro visto por primera vez en NIST NVD | |
| Monitoreo | Fuente: ENISA EUVD | Registro visto por primera vez en ENISA EUVD | |
| Divulgación | Evaluación SSVC | CISA-ADP · explotación ninguna | |
| Divulgación | Modificada | Última actualización del registro | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
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.
Affects Apache WSS4J deployments with a replay cache configured, as Apache CXF has by default. Fixed in 4.0.3, 3.0.7 and 2.4.5.
Descripción original del registro (apache)
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.
Condiciones y alcance
Desglose de métricas
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
org/apache:wss4j:wss4j-ws-security-common |
Corregida | 2.4.5, 3.0.7, 4.0.3 | — | — |
2.4.53.0.74.0.3Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://lists.apache.org/thread.html/y2gb5of7tbh08zqv8rlh8212720f6tcyhttp://www.openwall.com/lists/oss-security/2026/11/16/4Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
