CVE-2026-68495
The CBOR parser in FasterXML jackson-dataformats-binary never invokes StreamReadConstraints.validateNameLength() when decoding JSON object property names, so the maxNameLength limit is not enforced for this format. CBORParser._decodeLongerName() decodes a definite-length property name with no length check, and CBORParser._decodeChunkedName() delegates to the value-oriented _finishChunkedText() routine, which validates maxStringLength rather than maxNameLength.
Leer descripción completaMostrar menos
An attacker who can have a CBOR document parsed may therefore embed a single property name of unbounded length; the parser buffers the whole name in memory before returning it, whatever maxNameLength is configured to. Because StreamReadConstraints.maxDocumentLength is also disabled by default, nothing else bounds the name under default settings, so the only limits are the attacker's upload capacity and available heap, leading to memory exhaustion and denial of service. No privileges beyond the ability to submit data to a parsing endpoint are required, and exploitation needs only that the bytes reach CBORFactory parsing, directly or through an ObjectMapper configured with the CBOR module. jackson-core's own JSON parsers enforce maxNameLength incrementally during name decoding; this gap is specific to the binary formats. maxNameLength and validateNameLength were introduced in jackson-core 2.16.0, so releases before 2.16.0 do not contain the constraint that is left unenforced. This issue is tracked together with the Smile parser defect in the same vendor advisory, GHSA-3v8f-v6vx-fmrm, which covers both binary formats. The CBOR parser defect (jackson-dataformats-binary issue #725) is CVE-2026-68495; the Smile parser defect (issue #726) is assigned CVE-2026-68496.
CVSS
- Versión: 3.1
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Puntuación base: 7.5
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: 6/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 access95 % - Impacto principal
T1499.004Application or System Exploitationimpact90 %
Parser CBOR sin validación de longitud de nombres genera DoS por exhaustión de memoria; AV:N/AC:L/PR:N permite T1190; impacto es negación de disponibilidad (T1499.004).
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)
⚠ Inferidas por IA a partir de la descripción — NVD aún no ha analizado esta CVE; no son CPE verificados.
CWE
- CWE-400, CWE-770
Referencias
- https://github.com/FasterXML/jackson-dataformats-binary/blob/2.18/release-notes/VERSION-2.x
- https://github.com/FasterXML/jackson-dataformats-binary/issues/725
- https://github.com/FasterXML/jackson-dataformats-binary/security/advisories/GHSA-3v8f-v6vx-fmrm
- https://www.cve.org/CVERecord?id=CVE-2026-68496
- https://github.com/FasterXML/jackson-dataformats-binary/security/advisories/GHSA-3v8f-v6vx-fmrm
JSON original (NVD)
Mostrar
{
"id": "CVE-2026-68495",
"cveTags": [],
"metrics": {
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2026-68495",
"role": "CISA Coordinator",
"options": [
{
"exploitation": "poc"
},
{
"automatable": "yes"
},
{
"technicalImpact": "partial"
}
],
"version": "2.0.3",
"timestamp": "2026-10-01T18:16:18.497961Z"
}
}
],
"cvssMetricV31": [
{
"type": "Secondary",
"source": "36c7be3b-2937-45df-85ea-ca7133ea542c",
"cvssData": {
"scope": "UNCHANGED",
"version": "3.1",
"baseScore": 7.5,
"attackVector": "NETWORK",
"baseSeverity": "HIGH",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"integrityImpact": "NONE",
"userInteraction": "NONE",
"attackComplexity": "LOW",
"availabilityImpact": "HIGH",
"privilegesRequired": "NONE",
"confidentialityImpact": "NONE"
},
"impactScore": 3.6,
"exploitabilityScore": 3.9
}
]
},
"affected": [
{
"source": "36c7be3b-2937-45df-85ea-ca7133ea542c",
"affectedData": [
{
"repo": "https://github.com/FasterXML/jackson-dataformats-binary",
"vendor": "FasterXML",
"product": "jackson-dataformats-binary",
"versions": [
{
"status": "affected",
"version": "2.16.0",
"versionType": "maven",
"lessThanOrEqual": "2.18.9"
},
{
"status": "affected",
"version": "2.19.0",
"versionType": "maven",
"lessThanOrEqual": "2.21.5"
},
{
"status": "affected",
"version": "2.22.0",
"versionType": "maven",
"lessThanOrEqual": "2.22.1"
}
],
"packageName": "com.fasterxml.jackson.dataformat:jackson-dataformat-cbor",
"collectionURL": "https://repo1.maven.org/maven2",
"defaultStatus": "unaffected",
"programRoutines": [
{
"name": "com.fasterxml.jackson.dataformat.cbor.CBORParser._decodeLongerName"
},
{
"name": "com.fasterxml.jackson.dataformat.cbor.CBORParser._decodeChunkedName"
}
]
},
{
"repo": "https://github.com/FasterXML/jackson-dataformats-binary",
"vendor": "FasterXML",
"product": "jackson-dataformats-binary",
"versions": [
{
"status": "affected",
"version": "3.0.0",
"versionType": "maven",
"lessThanOrEqual": "3.1.5"
},
{
"status": "affected",
"version": "3.2.0",
"versionType": "maven",
"lessThanOrEqual": "3.2.1"
}
],
"packageName": "tools.jackson.dataformat:jackson-dataformat-cbor",
"collectionURL": "https://repo1.maven.org/maven2",
"defaultStatus": "unaffected",
"programRoutines": [
{
"name": "tools.jackson.dataformat.cbor.CBORParser._decodeLongerName"
},
{
"name": "tools.jackson.dataformat.cbor.CBORParser._decodeChunkedName"
}
]
}
]
}
],
"published": "2026-10-01T18:17:27.167",
"references": [
{
"url": "https://github.com/FasterXML/jackson-dataformats-binary/blob/2.18/release-notes/VERSION-2.x",
"source": "36c7be3b-2937-45df-85ea-ca7133ea542c"
},
{
"url": "https://github.com/FasterXML/jackson-dataformats-binary/issues/725",
"source": "36c7be3b-2937-45df-85ea-ca7133ea542c"
},
{
"url": "https://github.com/FasterXML/jackson-dataformats-binary/security/advisories/GHSA-3v8f-v6vx-fmrm",
"source": "36c7be3b-2937-45df-85ea-ca7133ea542c"
},
{
"url": "https://www.cve.org/CVERecord?id=CVE-2026-68496",
"source": "36c7be3b-2937-45df-85ea-ca7133ea542c"
},
{
"url": "https://github.com/FasterXML/jackson-dataformats-binary/security/advisories/GHSA-3v8f-v6vx-fmrm",
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"
}
],
"vulnStatus": "Awaiting Analysis",
"weaknesses": [
{
"type": "Secondary",
"source": "36c7be3b-2937-45df-85ea-ca7133ea542c",
"description": [
{
"lang": "en",
"value": "CWE-400"
},
{
"lang": "en",
"value": "CWE-770"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "The CBOR parser in FasterXML jackson-dataformats-binary never invokes StreamReadConstraints.validateNameLength() when decoding JSON object property names, so the maxNameLength limit is not enforced for this format. CBORParser._decodeLongerName() decodes a definite-length property name with no length check, and CBORParser._decodeChunkedName() delegates to the value-oriented _finishChunkedText() routine, which validates maxStringLength rather than maxNameLength. An attacker who can have a CBOR document parsed may therefore embed a single property name of unbounded length; the parser buffers the whole name in memory before returning it, whatever maxNameLength is configured to. Because StreamReadConstraints.maxDocumentLength is also disabled by default, nothing else bounds the name under default settings, so the only limits are the attacker's upload capacity and available heap, leading to memory exhaustion and denial of service. No privileges beyond the ability to submit data to a parsing endpoint are required, and exploitation needs only that the bytes reach CBORFactory parsing, directly or through an ObjectMapper configured with the CBOR module. jackson-core's own JSON parsers enforce maxNameLength incrementally during name decoding; this gap is specific to the binary formats. maxNameLength and validateNameLength were introduced in jackson-core 2.16.0, so releases before 2.16.0 do not contain the constraint that is left unenforced. This issue is tracked together with the Smile parser defect in the same vendor advisory, GHSA-3v8f-v6vx-fmrm, which covers both binary formats. The CBOR parser defect (jackson-dataformats-binary issue #725) is CVE-2026-68495; the Smile parser defect (issue #726) is assigned CVE-2026-68496."
}
],
"lastModified": "2026-10-02T18:44:11.270",
"sourceIdentifier": "36c7be3b-2937-45df-85ea-ca7133ea542c"
}