CVE-2025-57735
When user logged out, the JWT token the user had authtenticated with was not invalidated, which could lead to reuse of that token in case it was intercepted. In Airflow 3.2 we implemented the mechanism that implements token invalidation at logout. Users who are concerned about the logout scenario and possibility of intercepting the tokens, should upgrade to Airflow 3.2+
Users are recommended to upgrade to version 3.2.0, which fixes this issue.
CVSS
- Versión: 3.1
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
- Puntuación base: 9.1
Probabilidad de explotación (EPSS)
- Probabilidad de explotación en los próximos 30 días: 0.67%
- Percentil entre todas las CVEs puntuadas: 50
- Fecha de la puntuación: 4/10/2026
EPSS (Exploit Prediction Scoring System, de FIRST) estima la probabilidad de que una vulnerabilidad sea explotada en 30 días. Complementa a CVSS (impacto) y a CISA KEV (explotación confirmada).
🎯 Técnicas ATT&CK
Cómo se explota esta vulnerabilidad y qué consigue el atacante, en el lenguaje de MITRE ATT&CK.
- Explotación
T1190Exploit Public-Facing Applicationinitial access75 % - Impacto principal
T1078.004Cloud Accountsstealth · persistence · privilege escalation · initial access80 % - Impacto secundario
T1550.001Application Access Tokenlateral movement75 %
Vector CVSS N/N/N indica red sin autenticación. JWT no invalidado en logout permite reutilización de token interceptado para acceso no autorizado persistente.
Inferido por nuestro agente de análisis a partir de la descripción oficial, el vector CVSS y la CWE, y comprobado por un supervisor. Puede contener errores.
🛡️ Mitigaciones ATT&CK que cubren estas técnicas
Tecnologías afectadas (1)
CWE
- CWE-613
Referencias
JSON original (NVD)
Mostrar
{
"id": "CVE-2025-57735",
"cveTags": [],
"metrics": {
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2025-57735",
"role": "CISA Coordinator",
"options": [
{
"exploitation": "none"
},
{
"automatable": "yes"
},
{
"technicalImpact": "partial"
}
],
"version": "2.0.3",
"timestamp": "2026-04-09T13:53:16.618977Z"
}
}
],
"cvssMetricV31": [
{
"type": "Secondary",
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"cvssData": {
"scope": "UNCHANGED",
"version": "3.1",
"baseScore": 9.1,
"attackVector": "NETWORK",
"baseSeverity": "CRITICAL",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N",
"integrityImpact": "HIGH",
"userInteraction": "NONE",
"attackComplexity": "LOW",
"availabilityImpact": "NONE",
"privilegesRequired": "NONE",
"confidentialityImpact": "HIGH"
},
"impactScore": 5.2,
"exploitabilityScore": 3.9
}
]
},
"affected": [
{
"source": "security@apache.org",
"affectedData": [
{
"vendor": "Apache Software Foundation",
"product": "Apache Airflow",
"versions": [
{
"status": "affected",
"version": "3.0.0",
"lessThan": "3.2.0",
"versionType": "semver"
}
],
"packageName": "apache-airflow",
"collectionURL": "https://pypi.python.org",
"defaultStatus": "unaffected"
}
]
}
],
"published": "2026-04-09T11:16:20.757",
"references": [
{
"url": "https://github.com/apache/airflow/pull/56633",
"tags": [
"Issue Tracking"
],
"source": "security@apache.org"
},
{
"url": "https://github.com/apache/airflow/pull/61339",
"tags": [
"Issue Tracking"
],
"source": "security@apache.org"
},
{
"url": "https://lists.apache.org/thread/ovn8mpd8zkc604hojt7x3wsw3kc60x98",
"tags": [
"Mailing List",
"Vendor Advisory"
],
"source": "security@apache.org"
},
{
"url": "http://www.openwall.com/lists/oss-security/2026/04/09/16",
"tags": [
"Mailing List",
"Third Party Advisory"
],
"source": "af854a3a-2127-422b-91ae-364da2661108"
}
],
"vulnStatus": "Analyzed",
"weaknesses": [
{
"type": "Secondary",
"source": "security@apache.org",
"description": [
{
"lang": "en",
"value": "CWE-613"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "When user logged out, the JWT token the user had authtenticated with was not invalidated, which could lead to reuse of that token in case it was intercepted. In Airflow 3.2 we implemented the mechanism that implements token invalidation at logout. Users who are concerned about the logout scenario and possibility of intercepting the tokens, should upgrade to Airflow 3.2+\n\n\n\nUsers are recommended to upgrade to version 3.2.0, which fixes this issue."
},
{
"lang": "es",
"value": "Cuando el usuario cerró sesión, el token JWT con el que se había autenticado no fue invalidado, lo que podría llevar a la reutilización de ese token en caso de que fuera interceptado. En Airflow 3.2 implementamos el mecanismo que implementa la invalidación de tokens al cerrar sesión. Los usuarios que estén preocupados por el escenario de cierre de sesión y la posibilidad de interceptar los tokens, deberían actualizar a Airflow 3.2+.\n\nSe recomienda a los usuarios actualizar a la versión 3.2.0, que corrige este problema."
}
],
"lastModified": "2026-09-30T22:10:00.273",
"configurations": [
{
"nodes": [
{
"negate": false,
"cpeMatch": [
{
"criteria": "cpe:2.3:a:apache:airflow:*:*:*:*:*:*:*:*",
"vulnerable": true,
"matchCriteriaId": "D8133DE3-F556-42F5-8298-FD4CF40787B6",
"versionEndExcluding": "3.2.0",
"versionStartIncluding": "3.0.0"
}
],
"operator": "OR"
}
]
}
],
"sourceIdentifier": "security@apache.org"
}