ppkarwasz opened a new pull request, #22:
URL: https://github.com/apache/logging-site/pull/22

   Adds 8 new CVEs to the VDR and vulnerability page for the Log4j 2.25.4, 
Log4cxx 1.7.0, and Log4net 3.3.0 releases, and
   extends the component list to support the new entries.
   
   ### New CVEs
   
   | CVE            | Component                    | Summary                    
                                                           |
   
|----------------|------------------------------|---------------------------------------------------------------------------------------|
   | CVE-2026-40023 | Log4cxx                      | Silent log event loss in 
`XMLLayout` (XML 1.0 forbidden chars)                        |
   | CVE-2026-40021 | Log4net                      | Silent log event loss in 
`XmlLayout`/`XmlLayoutSchemaLog4J` (XML 1.0 forbidden chars) |
   | CVE-2026-34481 | `log4j-layout-template-json` | Non-finite floats produce 
invalid JSON in `JsonTemplateLayout`                        |
   | CVE-2026-34480 | `log4j-core`                 | Silent log event loss in 
`XmlLayout` (XML 1.0 forbidden chars)                        |
   | CVE-2026-34479 | `log4j-1.2-api`              | Silent log event loss in 
`Log4j1XmlLayout` (XML 1.0 forbidden chars)                  |
   | CVE-2026-34478 | `log4j-core`                 | Log injection in 
`Rfc5424Layout` via silent attribute renames                         |
   | CVE-2026-34477 | `log4j-core`                 | `verifyHostName` attribute 
silently ignored in TLS configuration                      |
   | CVE-2025-68161 | `log4j-core`                 | Update affected version 
range to include 3.0.0 pre-releases                           |
   
   ### Other changes
   
   - Add `log4cxx` CPE, `log4cxx-conan`, `log4j-1.2-api`, 
`log4j-layout-template-json`, and `log4net` components to the VDR
   - Fix `<ref>` typo `logcxx` → `log4cxx` in CVE-2025-54813 and CVE-2025-54812


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to