{"items":[{"id":"NVI-00010692","kind":"vulnerability","title":"Apache Log4j 1 to Log4j 2 bridge: silent log event loss in Log4j1XmlLayout due to unescaped XML 1.0 forbidden characters","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-h383-gmxw-35v2","CVE-2026-34479"],"plain_summary":"GitHub lists this reviewed advisory for org.apache.logging.log4j:log4j-core, org.apache.logging.log4j:log4j-core. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-182209fcefd5fdc6a0b8675461152b77"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.535%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.45147. Missing scores are unknown.","source_id":"sr-182209fcefd5fdc6a0b8675461152b77"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-a9e76f3ea3b9d279669ed29b88f3fd3b","url":"https://github.com/advisories/GHSA-h383-gmxw-35v2","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-h383-gmxw-35v2","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T22:06:46.371Z"},{"id":"sr-182209fcefd5fdc6a0b8675461152b77","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-34479","publisher":"FIRST EPSS","observed_at":"2026-10-31T23:13:27.693Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-a9e76f3ea3b9d279669ed29b88f3fd3b"],"technology":"org.apache.logging.log4j:log4j-core","known_exclusions":[],"conditions_summary":"The `Log4j1XmlLayout` from the Apache Log4j 1-to-Log4j 2 bridge fails to escape characters forbidden by the XML 1.0 standard, producing malformed XML output. Conforming XML parsers are required to reject documents containing such characters with a fatal error, which may cause downstream log processing systems to drop or fail to index affected records.\n\nTwo groups of users are affected:\n\n* Those using `Log4j1XmlLayout` directly in a Log4j Core 2 configuration file.\n* Those using the Log4j 1 configuration compatibility layer with `org.apache.log4j.xml.XMLLayout` specified as the layout class.\n\nUsers are advised to upgrade to Apache Log4j 1-to-Log4j 2 bridge version `2.25.4`, which corrects this issue.\n\n> [!NOTE]\n> The Apache Log4j 1-to-Log4j 2 bridge is deprecated and will not be present in Log4j 3. Users are encouraged to consult the\n> Log4j 1 to Log4j 2 migration guide, and specifically the section on eliminating reliance on the bridge.","public_affected_ranges":[">= 2.7, < 2.25.4"]},{"certainty":"source_listed","source_ids":["sr-a9e76f3ea3b9d279669ed29b88f3fd3b"],"technology":"org.apache.logging.log4j:log4j-core","known_exclusions":[],"conditions_summary":"The `Log4j1XmlLayout` from the Apache Log4j 1-to-Log4j 2 bridge fails to escape characters forbidden by the XML 1.0 standard, producing malformed XML output. Conforming XML parsers are required to reject documents containing such characters with a fatal error, which may cause downstream log processing systems to drop or fail to index affected records.\n\nTwo groups of users are affected:\n\n* Those using `Log4j1XmlLayout` directly in a Log4j Core 2 configuration file.\n* Those using the Log4j 1 configuration compatibility layer with `org.apache.log4j.xml.XMLLayout` specified as the layout class.\n\nUsers are advised to upgrade to Apache Log4j 1-to-Log4j 2 bridge version `2.25.4`, which corrects this issue.\n\n> [!NOTE]\n> The Apache Log4j 1-to-Log4j 2 bridge is deprecated and will not be present in Log4j 3. Users are encouraged to consult the\n> Log4j 1 to Log4j 2 migration guide, and specifically the section on eliminating reliance on the bridge.","public_affected_ranges":[">= 3.0.0-beta1, <= 3.0.0-beta2"]}],"null_published_at":"2026-10-31T23:18:22.440Z","source_updated_at":"2026-10-26T15:16:51.000Z","source_disclosed_at":"2026-04-10T18:31:18.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T22:06:46.371Z"},{"id":"NVI-00010692","kind":"vulnerability","title":"Apache Log4j 1 to Log4j 2 bridge: silent log event loss in Log4j1XmlLayout due to unescaped XML 1.0 forbidden characters","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-h383-gmxw-35v2","CVE-2026-34479"],"plain_summary":"GitHub lists this reviewed advisory for org.apache.logging.log4j:log4j-core, org.apache.logging.log4j:log4j-core. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-a9e76f3ea3b9d279669ed29b88f3fd3b"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-a9e76f3ea3b9d279669ed29b88f3fd3b","url":"https://github.com/advisories/GHSA-h383-gmxw-35v2","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-h383-gmxw-35v2","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T22:06:46.371Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-a9e76f3ea3b9d279669ed29b88f3fd3b"],"technology":"org.apache.logging.log4j:log4j-core","known_exclusions":[],"conditions_summary":"The `Log4j1XmlLayout` from the Apache Log4j 1-to-Log4j 2 bridge fails to escape characters forbidden by the XML 1.0 standard, producing malformed XML output. Conforming XML parsers are required to reject documents containing such characters with a fatal error, which may cause downstream log processing systems to drop or fail to index affected records.\n\nTwo groups of users are affected:\n\n* Those using `Log4j1XmlLayout` directly in a Log4j Core 2 configuration file.\n* Those using the Log4j 1 configuration compatibility layer with `org.apache.log4j.xml.XMLLayout` specified as the layout class.\n\nUsers are advised to upgrade to Apache Log4j 1-to-Log4j 2 bridge version `2.25.4`, which corrects this issue.\n\n> [!NOTE]\n> The Apache Log4j 1-to-Log4j 2 bridge is deprecated and will not be present in Log4j 3. Users are encouraged to consult the\n> Log4j 1 to Log4j 2 migration guide, and specifically the section on eliminating reliance on the bridge.","public_affected_ranges":[">= 2.7, < 2.25.4"]},{"certainty":"source_listed","source_ids":["sr-a9e76f3ea3b9d279669ed29b88f3fd3b"],"technology":"org.apache.logging.log4j:log4j-core","known_exclusions":[],"conditions_summary":"The `Log4j1XmlLayout` from the Apache Log4j 1-to-Log4j 2 bridge fails to escape characters forbidden by the XML 1.0 standard, producing malformed XML output. Conforming XML parsers are required to reject documents containing such characters with a fatal error, which may cause downstream log processing systems to drop or fail to index affected records.\n\nTwo groups of users are affected:\n\n* Those using `Log4j1XmlLayout` directly in a Log4j Core 2 configuration file.\n* Those using the Log4j 1 configuration compatibility layer with `org.apache.log4j.xml.XMLLayout` specified as the layout class.\n\nUsers are advised to upgrade to Apache Log4j 1-to-Log4j 2 bridge version `2.25.4`, which corrects this issue.\n\n> [!NOTE]\n> The Apache Log4j 1-to-Log4j 2 bridge is deprecated and will not be present in Log4j 3. Users are encouraged to consult the\n> Log4j 1 to Log4j 2 migration guide, and specifically the section on eliminating reliance on the bridge.","public_affected_ranges":[">= 3.0.0-beta1, <= 3.0.0-beta2"]}],"null_published_at":"2026-10-31T22:27:12.375Z","source_updated_at":"2026-10-26T15:16:51.000Z","source_disclosed_at":"2026-04-10T18:31:18.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T22:06:46.371Z"}],"next_cursor":null,"snapshot_revision":"42594"}