CVE-2026-34478

{"id": "CVE-2026-34478", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-34478", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "yes"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2026-04-10T17:48:27.852992Z"}}], "cvssMetricV31": [{"type": "Primary", "source": "nvd@nist.gov", "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:H/A:N", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}, "impactScore": 3.6, "exploitabilityScore": 3.9}], "cvssMetricV40": [{"type": "Secondary", "source": "security@apache.org", "cvssData": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 6.9, "Automatable": "NOT_DEFINED", "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "valueDensity": "NOT_DEFINED", "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X", "exploitMaturity": "NOT_DEFINED", "providerUrgency": "NOT_DEFINED", "userInteraction": "NONE", "attackComplexity": "LOW", "attackRequirements": "NONE", "privilegesRequired": "NONE", "subIntegrityImpact": "LOW", "vulnIntegrityImpact": "NONE", "integrityRequirement": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "subAvailabilityImpact": "NONE", "vulnAvailabilityImpact": "NONE", "availabilityRequirement": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "subConfidentialityImpact": "NONE", "vulnConfidentialityImpact": "NONE", "confidentialityRequirement": "NOT_DEFINED", "modifiedAttackRequirements": "NOT_DEFINED", "modifiedPrivilegesRequired": "NOT_DEFINED", "modifiedSubIntegrityImpact": "NOT_DEFINED", "modifiedVulnIntegrityImpact": "NOT_DEFINED", "vulnerabilityResponseEffort": "NOT_DEFINED", "modifiedSubAvailabilityImpact": "NOT_DEFINED", "modifiedVulnAvailabilityImpact": "NOT_DEFINED", "modifiedSubConfidentialityImpact": "NOT_DEFINED", "modifiedVulnConfidentialityImpact": "NOT_DEFINED"}}]}, "affected": [{"source": "security@apache.org", "affectedData": [{"cpes": ["cpe:2.3:a:apache:log4j:*:*:*:*:*:*:*:*"], "vendor": "Apache Software Foundation", "product": "Apache Log4j Core", "versions": [{"status": "affected", "version": "2.21.0", "lessThan": "2.25.4", "versionType": "maven"}, {"status": "affected", "version": "3.0.0-beta1", "versionType": "maven", "lessThanOrEqual": "3.0.0-beta3"}], "packageURL": "pkg:maven/org.apache.logging.log4j/log4j-core", "packageName": "org.apache.logging.log4j:log4j-core", "collectionURL": "https://repo.maven.apache.org/maven2", "defaultStatus": "unaffected"}]}], "published": "2026-04-10T16:16:31.070", "references": [{"url": "https://github.com/apache/logging-log4j2/pull/4074", "tags": ["Issue Tracking", "Patch"], "source": "security@apache.org"}, {"url": "https://lists.apache.org/thread/3k1clr2l6vkdnl4cbhjrnt1nyjvb5gwt", "tags": ["Mailing List", "Vendor Advisory"], "source": "security@apache.org"}, {"url": "https://logging.apache.org/cyclonedx/vdr.xml", "tags": ["Product"], "source": "security@apache.org"}, {"url": "https://logging.apache.org/log4j/2.x/manual/layouts.html#RFC5424Layout", "tags": ["Technical Description"], "source": "security@apache.org"}, {"url": "https://logging.apache.org/security.html#CVE-2026-34478", "tags": ["Vendor Advisory"], "source": "security@apache.org"}, {"url": "http://www.openwall.com/lists/oss-security/2026/04/10/7", "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-117"}, {"lang": "en", "value": "CWE-684"}]}], "descriptions": [{"lang": "en", "value": "Apache Log4j Core's Rfc5424Layout https://logging.apache.org/log4j/2.x/manual/layouts.html#RFC5424Layout , in versions 2.21.0 through 2.25.3, is vulnerable to log injection via CRLF sequences due to undocumented renames of security-relevant configuration attributes.\n\nTwo distinct issues affect users of stream-based syslog services who configure Rfc5424Layout directly:\n\n * The newLineEscape attribute was silently renamed, causing newline escaping to stop working for users of TCP framing (RFC 6587), exposing them to CRLF injection in log output.\n * The useTlsMessageFormat attribute was silently renamed, causing users of TLS framing (RFC 5425) to be silently downgraded to unframed TCP (RFC 6587), without newline escaping.\n\n\nUsers of the SyslogAppender are not affected, as its configuration attributes were not modified.\n\nUsers are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue."}, {"lang": "es", "value": "El Rfc5424Layout de Apache Log4j Core https://logging.apache.org/log4j/2.x/manual/layouts.html#RFC5424Layout , en las versiones 2.21.0 a 2.25.3, es vulnerable a la inyecci\u00f3n de registros a trav\u00e9s de secuencias CRLF debido a cambios de nombre no documentados de atributos de configuraci\u00f3n relevantes para la seguridad.\n\nDos problemas distintos afectan a los usuarios de servicios syslog basados en flujo que configuran Rfc5424Layout directamente:\n\n * El atributo newLineEscape fue renombrado silenciosamente, lo que provoc\u00f3 que el escape de nueva l\u00ednea dejara de funcionar para los usuarios de tramas TCP (RFC 6587), exponi\u00e9ndolos a la inyecci\u00f3n de CRLF en la salida de registros.\n * El atributo useTlsMessageFormat fue renombrado silenciosamente, lo que provoc\u00f3 que los usuarios de tramas TLS (RFC 5425) fueran degradados silenciosamente a TCP sin tramas (RFC 6587), sin escape de nueva l\u00ednea.\n\nLos usuarios del SyslogAppender no se ven afectados, ya que sus atributos de configuraci\u00f3n no fueron modificados.\n\nSe aconseja a los usuarios actualizar a Apache Log4j Core 2.25.4, que corrige este problema."}], "lastModified": "2026-10-26T22:10:00.163", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:apache:log4j:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "4928759D-3A0D-4BC2-85BC-2CFAF137B4A0", "versionEndExcluding": "2.25.4", "versionStartIncluding": "2.21.0"}, {"criteria": "cpe:2.3:a:apache:log4j:3.0.0:beta1:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "ED00C38D-27EA-489C-9A2B-3594ACA8A3C5"}, {"criteria": "cpe:2.3:a:apache:log4j:3.0.0:beta2:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "8794D719-1D90-4378-B48B-698EA40FBFB2"}, {"criteria": "cpe:2.3:a:apache:log4j:3.0.0:beta3:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "74C9FCBD-ECAD-4C29-B97A-2B9D97C0FC1F"}], "operator": "OR"}]}], "sourceIdentifier": "security@apache.org"}