BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-34481High confidence

Apache Log4j JSON Template Layout: Improper serialization of non-finite floating-point values in JsonTemplateLayout

Apache Software Foundation · Apache Log4j JSON Template Layout

6.3MediumCVSS 4.0
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 4 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Medium, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.85% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Apache Software Foundation Apache Log4j JSON Template Layout and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 4 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

10 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 4 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourceapache-log4j1.2Not affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian trixietrixie · sourceapache-log4j2Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourceapache-log4j1.2Not affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourceapache-log4j2Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourceapache-log4j1.2Not affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourceapache-log4j2Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourceapache-log4j1.2Not affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourceapache-log4j2Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archiveapache-log4j1.2Under evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archiveapache-log4j2Under evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Open-source package ranges4 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
Mavenorg.apache.logging.log4j:log4j-layout-template-jsonECOSYSTEM: introduced 2.14.0; fixed 2.25.42.25.4OSV record ↗aggregator derived · 10 Sep 2026
Mavenorg.apache.logging.log4j:log4j-layout-template-jsonECOSYSTEM: introduced 3.0.0-alpha1; last affected 3.0.0-beta3Not statedOSV record ↗aggregator derived · 10 Sep 2026
mavenorg.apache.logging.log4j:log4j-layout-template-json>= 2.14.0, < 2.25.42.25.4GitHub advisory ↗github reviewed aggregator · 13 Apr 2026
mavenorg.apache.logging.log4j:log4j-layout-template-json>= 3.0.0-alpha1, <= 3.0.0-beta3Not statedGitHub advisory ↗github reviewed aggregator · 13 Apr 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-34481 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityorg.apache.logging.log4j: Apache Log4j JsonTemplateLayout: Denial of Service via invalid JSON output
4 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • log4j-jcl as a component of Red Hat Enterprise Linux 9
  • log4j-slf4j as a component of Red Hat Enterprise Linux 9
  • log4j.src as a component of Red Hat Enterprise Linux 9
  • log4j-layout-template-json as a component of Red Hat JBoss Enterprise Application Platform 7
Summary
A flaw was found in Apache Log4j's JsonTemplateLayout. This vulnerability allows a remote attacker to disrupt log processing systems. By sending log events that include specific non-numeric floating-point values, the attacker can cause the JsonTemplateLayout to generate invalid JSON output. This invalid output can then lead to downstream systems rejecting or failing to index these logs, effectively causing a denial of service for log analysis.
Remediation
Before applying the update, back up your existing installation, including all applications, configuration files, databases and database settings. The References section of this erratum contains a download link (you must log in to download the update).
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-21412

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 4 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

Apache Log4j's JsonTemplateLayout https://logging.apache.org/log4j/2.x/manual/json-template-layout.html , in versions up to and including 2.25.3, produces invalid JSON output when log events contain non-finite floating-point values (NaN, Infinity, or -Infinity), which are prohibited by RFC 8259. This may cause downstream log processing systems to reject or fail to index affected records. An attacker can exploit this issue only if both of the following conditions are met: * The application uses JsonTemplateLayout. * The application logs a MapMessage, or logs an object directly (e.g., via Logger.info(Object), which wraps it in an ObjectMessage), where the message contains an attacker-controlled floating-point value. Users are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue. Note: The fix released in version 2.25.4 did not cover all affected code paths. CVE-2026-49844 was assigned to the remaining issue, which concerns the MapMessage.asJson() serialization in Apache Log4j API and is fixed in versions 2.25.5 and 2.26.1.

What

Apache Log4j's JsonTemplateLayout https://logging.apache.org/log4j/2.x/manual/json-template-layout.html , in versions up to and including 2.25.3, produces invalid JSON output when log events contain non-finite floating-point values (NaN, Infinity, or -Infinity), which are prohibited by RFC 8259. This may cause downstream log processing systems to reject or fail to index affected records. An attacker can exploit this issue only if both of the following conditions are met: * The application uses JsonTemplateLayout. * The application logs a MapMessage, or logs an object directly (e.g., via Logger.info(Object), which wraps it in an ObjectMessage), where the message contains an attacker-controlled floating-point value. Users are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue. Note: The fix released in version 2.25.4 did not cover all affected code paths. CVE-2026-49844 was assigned to the remaining issue, which concerns the MapMessage.asJson() serialization in Apache Log4j API and is fixed in versions 2.25.5 and 2.26.1.

Why

The product prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. As a result, the intended structure of the message is not preserved.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

Apache Log4j's JsonTemplateLayout https://logging.apache.org/log4j/2.x/manual/json-template-layout.html , in versions up to and including 2.25.3, produces invalid JSON output when log events contain non-finite floating-point values (NaN, Infinity, or -Infinity), which are prohibited by RFC 8259. This may cause downstream log processing systems to reject or fail to index affected records. An attacker can exploit this issue only if both of the following conditions are met: * The application uses JsonTemplateLayout. * The application logs a MapMessage, or logs an object directly (e.g., via Logger.info(Object), which wraps it in an ObjectMessage), where the message contains an attacker-controlled floating-point value. Users are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue. Note: The fix released in version 2.25.4 did not cover all affected code paths. CVE-2026-49844 was assigned to the remaining issue, which concerns the MapMessage.asJson() serialization in Apache Log4j API and is fixed in versions 2.25.5 and 2.26.1.

Why

The product prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. As a result, the intended structure of the message is not preserved.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Improper Encoding or Escaping of Output → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
High: exploitation depends on specific conditions
Security boundary
Not a CVSS 4.0 base metric
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-116 ↗

CWE-116: Improper Encoding or Escaping of Output. The product prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. As a result, the intended structure of the message is not preserved.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N

Common Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.ATPresentAttack requirements: A particular deployment or execution condition must be present.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.VCNoneVulnerable-system confidentiality: No direct loss is represented by this metric.VINoneVulnerable-system integrity: No direct loss is represented by this metric.VANoneVulnerable-system availability: No direct loss is represented by this metric.SCNoneSubsequent-system confidentiality: No direct loss is represented by this metric.SILowSubsequent-system integrity: A successful attack can cause a limited loss.SANoneSubsequent-system availability: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-116
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-2890Oracle Enterprise Manager: Mehrere Schwachstellen

Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle Enterprise Manager ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2026-2893Oracle Hyperion: Mehrere Schwachstellen

Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle Hyperion ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2026-2895Oracle Financial Services Applications: Mehrere Schwachstellen

Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle Financial Services Applications ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2026-2899Oracle Supply Chain: Mehrere Schwachstellen

Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle Supply Chain ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2026-2437Oracle Communications: Mehrere Schwachstellen

Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle Communications ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2026-2444Oracle Fusion Middleware: Mehrere Schwachstellen

Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle Fusion Middleware ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2026-2450Oracle Supply Chain: Mehrere Schwachstellen

Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle Supply Chain ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2026-2448Oracle Utilities Applications: Mehrere Schwachstellen

Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle Utilities Applications ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2026-2445Oracle Financial Services Applications: Mehrere Schwachstellen

Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle Financial Services Applications ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2026-2439Oracle Retail Applications: Mehrere Schwachstellen

Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle Retail Applications ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2026-2436Oracle Construction and Engineering: Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Oracle Construction and Engineering ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2026-2260IBM Operational Decision Manager: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM Operational Decision Manager ausnutzen, um beliebigen Programmcode auszuführen, um seine Privilegien zu erhöhen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, um Dateien zu manipulieren, und um Sicherheitsvorkehrungen zu umgehen.

Official advisory ↗
BSI · German · WID-SEC-2026-1943Oracle Enterprise Manager: Mehrere Schwachstellen

Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle Enterprise Manager ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2026-2901Oracle Retail Applications: Schwachstelle gefährdet Integrität

Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Oracle Retail Applications ausnutzen, um die Integrität zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2026-2432Oracle Spatial Studio: Schwachstelle gefährdet Integrität

Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Oracle Spatial Studio ausnutzen, um die Integrität zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2026-1942Oracle Communications: Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Oracle Communications ausnutzen, um die Vertraulichkeit und Integrität zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2026-1067Apache log4j: Mehrere Schwachstellen ermöglichen Manipulation von Dateien

Ein Angreifer kann mehrere Schwachstellen in Apache log4j ausnutzen, um Dateien zu manipulieren.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260415Security Bulletin 15 April 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 15 April 2026, published on 15 April 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1256Multiples vulnérabilités dans les produits IBM

d?id=CVE-2026-33672 Référence CVE CVE-2026-33750 https://www.cve.org/CVERecord?id=CVE-2026-33750 Référence CVE CVE-2026-34043 https://www.cve.org/CVERecord?id=CVE-2026-34043 Référence CVE CVE-2026-34355 https://www.cve.org/CVERecord?id=CVE-2026-34355 Référence CVE CVE-2026-34356 https://www.cve.org/CVERecord?id=CVE-2026-34356 Référence CVE CVE-2026-34477 https://www.cve.org/CVERecord?id=CVE-2026-34477 Référence CVE CVE-2026-34478 https://www.cve.org/CVERecord?id=CVE-2026-34478 Référence CVE CVE-2026-34479 https://www.cve.org/CVERecord?id=CVE-2026-34479 Référence CVE CVE-2026-34480 https://www.cve.org/CVERecord?id=CVE-2026-34480 Référence CVE CVE-2026-34481 https://www.cve.org/CVERecord?id=CVE-2026-34481 Référence CVE CVE-2026-3449 https://www.cve.org/CVERecord?id=CVE-2026-3449 Référence CVE CVE-2026-3520 https://www.cve.org/CVERecord?id=CVE-2026-3520 Référence CVE CVE-2026-39865 https://www.cve.org/CVERecord?id=CVE-2026-39865 Référence CVE CVE-2026-40175 https://www.cve.org/CVERecord?id=CVE-2026-40175 Référence CVE CVE-2026-40895 https://www.cve.org/CVERecord?id=CVE-2026-40895 Référence CVE CVE-2026-41238 https://www.cve.org/CVERecord?id=CVE-2026-41238 Référence CVE CVE-2026-41239 https://www.cve.org/CVERecord?id=CVE-2026-41239 Référence CVE CVE-2026-41240 https://www.cve.org/CVERecord?id=CVE-

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1206Multiples vulnérabilités dans les produits IBM

d?id=CVE-2026-33416 Référence CVE CVE-2026-34073 https://www.cve.org/CVERecord?id=CVE-2026-34073 Référence CVE CVE-2026-34197 https://www.cve.org/CVERecord?id=CVE-2026-34197 Référence CVE CVE-2026-34268 https://www.cve.org/CVERecord?id=CVE-2026-34268 Référence CVE CVE-2026-34282 https://www.cve.org/CVERecord?id=CVE-2026-34282 Référence CVE CVE-2026-34477 https://www.cve.org/CVERecord?id=CVE-2026-34477 Référence CVE CVE-2026-34478 https://www.cve.org/CVERecord?id=CVE-2026-34478 Référence CVE CVE-2026-34479 https://www.cve.org/CVERecord?id=CVE-2026-34479 Référence CVE CVE-2026-34480 https://www.cve.org/CVERecord?id=CVE-2026-34480 Référence CVE CVE-2026-34481 https://www.cve.org/CVERecord?id=CVE-2026-34481 Référence CVE CVE-2026-35536 https://www.cve.org/CVERecord?id=CVE-2026-35536 Référence CVE CVE-2026-3621 https://www.cve.org/CVERecord?id=CVE-2026-3621 Référence CVE CVE-2026-3713 https://www.cve.org/CVERecord?id=CVE-2026-3713 Référence CVE CVE-2026-39824 https://www.cve.org/CVERecord?id=CVE-2026-39824 Référence CVE CVE-2026-39892 https://www.cve.org/CVERecord?id=CVE-2026-39892 Référence CVE CVE-2026-40175 https://www.cve.org/CVERecord?id=CVE-2026-40175 Référence CVE CVE-2026-40192 https://www.cve.org/CVERecord?id=CVE-2026-40192 Référence CVE CVE-2026-40466 https://www.cve.org/CVERecord?id=CVE-

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1165Multiples vulnérabilités dans les produits IBM

rd?id=CVE-2026-2950 Référence CVE CVE-2026-32990 https://www.cve.org/CVERecord?id=CVE-2026-32990 Référence CVE CVE-2026-33671 https://www.cve.org/CVERecord?id=CVE-2026-33671 Référence CVE CVE-2026-33672 https://www.cve.org/CVERecord?id=CVE-2026-33672 Référence CVE CVE-2026-33814 https://www.cve.org/CVERecord?id=CVE-2026-33814 Référence CVE CVE-2026-34477 https://www.cve.org/CVERecord?id=CVE-2026-34477 Référence CVE CVE-2026-34478 https://www.cve.org/CVERecord?id=CVE-2026-34478 Référence CVE CVE-2026-34479 https://www.cve.org/CVERecord?id=CVE-2026-34479 Référence CVE CVE-2026-34480 https://www.cve.org/CVERecord?id=CVE-2026-34480 Référence CVE CVE-2026-34481 https://www.cve.org/CVERecord?id=CVE-2026-34481 Référence CVE CVE-2026-35091 https://www.cve.org/CVERecord?id=CVE-2026-35091 Référence CVE CVE-2026-35092 https://www.cve.org/CVERecord?id=CVE-2026-35092 Référence CVE CVE-2026-3621 https://www.cve.org/CVERecord?id=CVE-2026-3621 Référence CVE CVE-2026-38969 https://www.cve.org/CVERecord?id=CVE-2026-38969 Référence CVE CVE-2026-39865 https://www.cve.org/CVERecord?id=CVE-2026-39865 Référence CVE CVE-2026-40175 https://www.cve.org/CVERecord?id=CVE-2026-40175 Référence CVE CVE-2026-40181 https://www.cve.org/CVERecord?id=CVE-2026-40181 Référence CVE CVE-2026-40477 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1121Multiples vulnérabilités dans les produits IBM

d?id=CVE-2026-23865 Référence CVE CVE-2026-24733 https://www.cve.org/CVERecord?id=CVE-2026-24733 Référence CVE CVE-2026-24734 https://www.cve.org/CVERecord?id=CVE-2026-24734 Référence CVE CVE-2026-34268 https://www.cve.org/CVERecord?id=CVE-2026-34268 Référence CVE CVE-2026-34282 https://www.cve.org/CVERecord?id=CVE-2026-34282 Référence CVE CVE-2026-34477 https://www.cve.org/CVERecord?id=CVE-2026-34477 Référence CVE CVE-2026-34478 https://www.cve.org/CVERecord?id=CVE-2026-34478 Référence CVE CVE-2026-34479 https://www.cve.org/CVERecord?id=CVE-2026-34479 Référence CVE CVE-2026-34480 https://www.cve.org/CVERecord?id=CVE-2026-34480 Référence CVE CVE-2026-34481 https://www.cve.org/CVERecord?id=CVE-2026-34481 Référence CVE CVE-2026-41254 https://www.cve.org/CVERecord?id=CVE-2026-41254 Référence CVE CVE-2026-46917 https://www.cve.org/CVERecord?id=CVE-2026-46917 Référence CVE CVE-2026-46968 https://www.cve.org/CVERecord?id=CVE-2026-46968 Référence CVE CVE-2026-47010 https://www.cve.org/CVERecord?id=CVE-2026-47010 Référence CVE CVE-2026-47021 https://www.cve.org/CVERecord?id=CVE-2026-47021 Référence CVE CVE-2026-47027 https://www.cve.org/CVERecord?id=CVE-2026-47027 Référence CVE CVE-2026-47057 https://www.cve.org/CVERecord?id=CVE-2026-47057 Référence CVE CVE-2026-47058 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1094Multiples vulnérabilités dans les produits IBM

d?id=CVE-2026-33671 Référence CVE CVE-2026-33672 https://www.cve.org/CVERecord?id=CVE-2026-33672 Référence CVE CVE-2026-33750 https://www.cve.org/CVERecord?id=CVE-2026-33750 Référence CVE CVE-2026-33845 https://www.cve.org/CVERecord?id=CVE-2026-33845 Référence CVE CVE-2026-33846 https://www.cve.org/CVERecord?id=CVE-2026-33846 Référence CVE CVE-2026-34043 https://www.cve.org/CVERecord?id=CVE-2026-34043 Référence CVE CVE-2026-34197 https://www.cve.org/CVERecord?id=CVE-2026-34197 Référence CVE CVE-2026-34268 https://www.cve.org/CVERecord?id=CVE-2026-34268 Référence CVE CVE-2026-34282 https://www.cve.org/CVERecord?id=CVE-2026-34282 Référence CVE CVE-2026-34481 https://www.cve.org/CVERecord?id=CVE-2026-34481 Référence CVE CVE-2026-34513 https://www.cve.org/CVERecord?id=CVE-2026-34513 Référence CVE CVE-2026-34514 https://www.cve.org/CVERecord?id=CVE-2026-34514 Référence CVE CVE-2026-34515 https://www.cve.org/CVERecord?id=CVE-2026-34515 Référence CVE CVE-2026-34516 https://www.cve.org/CVERecord?id=CVE-2026-34516 Référence CVE CVE-2026-34517 https://www.cve.org/CVERecord?id=CVE-2026-34517 Référence CVE CVE-2026-34518 https://www.cve.org/CVERecord?id=CVE-2026-34518 Référence CVE CVE-2026-34519 https://www.cve.org/CVERecord?id=CVE-2026-34519 Référence CVE CVE-2026-34520 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1049Multiples vulnérabilités dans Oracle MySQL

/CVERecord?id=CVE-2026-0964 Référence CVE CVE-2026-0965 https://www.cve.org/CVERecord?id=CVE-2026-0965 Référence CVE CVE-2026-0966 https://www.cve.org/CVERecord?id=CVE-2026-0966 Référence CVE CVE-2026-0967 https://www.cve.org/CVERecord?id=CVE-2026-0967 Référence CVE CVE-2026-0968 https://www.cve.org/CVERecord?id=CVE-2026-0968 Référence CVE CVE-2026-34477 https://www.cve.org/CVERecord?id=CVE-2026-34477 Référence CVE CVE-2026-34478 https://www.cve.org/CVERecord?id=CVE-2026-34478 Référence CVE CVE-2026-34479 https://www.cve.org/CVERecord?id=CVE-2026-34479 Référence CVE CVE-2026-34480 https://www.cve.org/CVERecord?id=CVE-2026-34480 Référence CVE CVE-2026-34481 https://www.cve.org/CVERecord?id=CVE-2026-34481 Référence CVE CVE-2026-41238 https://www.cve.org/CVERecord?id=CVE-2026-41238 Référence CVE CVE-2026-41239 https://www.cve.org/CVERecord?id=CVE-2026-41239 Référence CVE CVE-2026-41240 https://www.cve.org/CVERecord?id=CVE-2026-41240 Référence CVE CVE-2026-49458 https://www.cve.org/CVERecord?id=CVE-2026-49458 Référence CVE CVE-2026-49459 https://www.cve.org/CVERecord?id=CVE-2026-49459 Référence CVE CVE-2026-49978 https://www.cve.org/CVERecord?id=CVE-2026-49978 Référence CVE CVE-2026-60592 https://www.cve.org/CVERecord?id=CVE-2026-60592 Référence CVE CVE-2026-65898 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0958Multiples vulnérabilités dans les produits IBM

d?id=CVE-2026-33846 Référence CVE CVE-2026-34040 https://www.cve.org/CVERecord?id=CVE-2026-34040 Référence CVE CVE-2026-34043 https://www.cve.org/CVERecord?id=CVE-2026-34043 Référence CVE CVE-2026-34197 https://www.cve.org/CVERecord?id=CVE-2026-34197 Référence CVE CVE-2026-34268 https://www.cve.org/CVERecord?id=CVE-2026-34268 Référence CVE CVE-2026-34477 https://www.cve.org/CVERecord?id=CVE-2026-34477 Référence CVE CVE-2026-34478 https://www.cve.org/CVERecord?id=CVE-2026-34478 Référence CVE CVE-2026-34479 https://www.cve.org/CVERecord?id=CVE-2026-34479 Référence CVE CVE-2026-34480 https://www.cve.org/CVERecord?id=CVE-2026-34480 Référence CVE CVE-2026-34481 https://www.cve.org/CVERecord?id=CVE-2026-34481 Référence CVE CVE-2026-34483 https://www.cve.org/CVERecord?id=CVE-2026-34483 Référence CVE CVE-2026-34487 https://www.cve.org/CVERecord?id=CVE-2026-34487 Référence CVE CVE-2026-3449 https://www.cve.org/CVERecord?id=CVE-2026-3449 Référence CVE CVE-2026-34500 https://www.cve.org/CVERecord?id=CVE-2026-34500 Référence CVE CVE-2026-3520 https://www.cve.org/CVERecord?id=CVE-2026-3520 Référence CVE CVE-2026-35554 https://www.cve.org/CVERecord?id=CVE-2026-35554 Référence CVE CVE-2026-39304 https://www.cve.org/CVERecord?id=CVE-2026-39304 Référence CVE CVE-2026-39821 https://www.cve.org/CVERecord?id=CVE-

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0920Multiples vulnérabilités dans Oracle Weblogic

tions Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation). Documentation Bulletin de sécurité Oracle Weblogic cpujul2026 du 21 juillet 2026 https://www.oracle.com/security-alerts/cpujul2026.html Référence CVE CVE-2025-68161 https://www.cve.org/CVERecord?id=CVE-2025-68161 Référence CVE CVE-2026-34477 https://www.cve.org/CVERecord?id=CVE-2026-34477 Référence CVE CVE-2026-34478 https://www.cve.org/CVERecord?id=CVE-2026-34478 Référence CVE CVE-2026-34479 https://www.cve.org/CVERecord?id=CVE-2026-34479 Référence CVE CVE-2026-34480 https://www.cve.org/CVERecord?id=CVE-2026-34480 Référence CVE CVE-2026-34481 https://www.cve.org/CVERecord?id=CVE-2026-34481 Référence CVE CVE-2026-5598 https://www.cve.org/CVERecord?id=CVE-2026-5598 Référence CVE CVE-2026-60153 https://www.cve.org/CVERecord?id=CVE-2026-60153 Référence CVE CVE-2026-60196 https://www.cve.org/CVERecord?id=CVE-2026-60196 Référence CVE CVE-2026-60198 https://www.cve.org/CVERecord?id=CVE-2026-60198 Référence CVE CVE-2026-60199 https://www.cve.org/CVERecord?id=CVE-2026-60199 Référence CVE CVE-2026-60200 https://www.cve.org/CVERecord?id=CVE-2026-60200 Référence CVE CVE-2026-60201 https://www.cve.org/CVERecord?id=CVE-2026-60201 Référence CVE CVE-2026-60202 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-012616Apache Software FoundationのApache Log4jにおけるエンコードおよびエスケープに関する脆弱性

Apache Log4jのJsonTemplateLayout（https://logging.apache.org/log4j/2.x/manual/json-template-layout.html）は、バージョン2.25.3まで（含む）において、ログイベントが非有限浮動小数点値（NaN、Infinity、または-Infinity）を含む場合に無効なJSON出力を生成します。これらの値はRFC 8259で禁止されており、その結果、下流のログ処理システムが影響を受けたレコードを拒否したり、インデックス作成に失敗したりする可能性があります。攻撃者がこの問題を悪用するには、以下の両方の条件を満たす必要があります。* アプリケーションがJsonTemplateLayoutを使用していること。* アプリケーションが攻撃者が制御する浮動小数点値を含むMapMessageをログに記録していること。ユーザーは、この問題を修正したApache Log4j JSON Template Layout 2.25.4へアップグレードすることを推奨します。

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-023805Apache Software FoundationのApache Log4jにおけるエンコードおよびエスケープに関する脆弱性

Apache Log4j APIにおけるMapMessageのJSONシリアライズ時に非有限浮動小数点値が不適切にエンコードされるため、有効なJSONではない出力が生成されます。この問題はApache Log4j APIのバージョン2.13.1から2.25.4およびバージョン2.26.0に影響します。CVE-2026-34481の修正はすべてのコード経路をカバーしておらず、MapMessageが非有限のIEEE 754値（NaN、Infinity、または-Infinity）を含む場合、MapMessage.asJson()は対応するベアトークンを出力します。RFC 8259はこれらのトークンを許可していないため、準拠したパーサーは生成されたドキュメントを拒否します。この欠陥は、次の両方の条件が満たされた場合にのみ発生します。・アプリケーションがJsonTemplateLayoutのメッセージリゾルバ（https://logging.apache.org/log4j/2.x/manual/json-template-layout.html#event-template-resolver-message）またはMapMessage.asJson()やMapMessage.getFormattedMessage(new String[]{"JSON"})に依存するその他のレイアウトを使用していること。・アプリケーションが攻撃者に制御された浮動小数点値を含むMapMessageをログ出力していること。攻撃者が非有限値を提供できる場合、影響を受けるレイアウトは不正なJSONを生成し、それがログレコード全体を破損させたり、下流のログ取り込みや解析を妨害したりする可能性があります。ユーザーには、Apache Log4j API 2.25.5または2.26.1へのアップグレードが推奨されており、これらのバージョンは非有限値に対してRFC 8259準拠のJSONを出力します。

Official advisory ↗
NCSC-NL · Dutch · NCSC-2026-0312Kwetsbaarheden verholpen in Oracle Financial Services

Apache Log4j JsonTemplateLayout up to version 2.25.3 improperly serializes non-finite floating-point values causing invalid JSON output, and multiple Oracle products using vulnerable Log4j versions are exposed to unauthenticated critical data modification with CVSS 7.5.

Official advisory ↗
NCSC-NL · Dutch · NCSC-2026-0311Kwetsbaarheden verholpen in Oracle Enterprise Manager

Apache Log4j JsonTemplateLayout up to version 2.25.3 improperly serializes non-finite floating-point values causing invalid JSON output, and multiple Oracle products using vulnerable Log4j versions are exposed to unauthenticated critical data modification with CVSS 7.5.

Official advisory ↗
NCSC-NL · Dutch · NCSC-2026-0258Kwetsbaarheden verholpen in Oracle Financial Services

Apache Log4j JsonTemplateLayout up to version 2.25.3 improperly serializes non-finite floating-point values, causing invalid JSON output and potential log processing failures, with critical vulnerabilities also affecting Oracle Enterprise Manager Base Platform.

Official advisory ↗
NCSC-NL · Dutch · NCSC-2026-0202Kwetsbaarheden verholpen in Oracle Enterprise Manager

Apache Log4j's JsonTemplateLayout up to version 2.25.3 improperly serializes non-finite floating-point values, producing invalid JSON that can disrupt log processing, while Oracle Enterprise Manager Base Platform versions 13.5 and 24.1 have a critical vulnerability allowing unauthenticated data modification.

Official advisory ↗
NCSC-NL · Dutch · NCSC-2026-0200Kwetsbaarheden verholpen in Oracle Communications

Apache Log4j's JsonTemplateLayout up to version 2.25.3 improperly serializes non-finite floating-point values, producing invalid JSON that can disrupt log processing, while Oracle Enterprise Manager Base Platform versions 13.5 and 24.1 have a critical vulnerability allowing unauthenticated data modification.

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 10 Apr 2026 · Last source change 11 Jul 2026, 04:55 UTC · CWE-116 · Improper Encoding or Escaping of Output

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-21412
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    log4j-jcl as a component of Red Hat Enterprise Linux 9; log4j-slf4j as a component of Red Hat Enterprise Linux 9; log4j.src as a component of Red Hat Enterprise Linux 9; log4j-layout-template-json as a component of Red Hat JBoss Enterprise Application Platform 7 · Fixed: Red Hat AMQ Broker 7.13.6; Red Hat AMQ Broker 7.14.1; Red Hat Data Grid 8.6.1; registry.redhat.io/offline-knowledge-portal/rhokp-rhel9@sha256:b26253f0a6c6b9e8c8458ecb07e79e9f87ff313491fffc31e342e32bce0a2b3e_arm64 as a component of Red Hat Offline Knowledge Portal 1.2.12; registry.redhat.io/offline-knowledge-portal/rhokp-rhel9@sha256:ec8b14b7a170b689a19cee7820888e81ddc3affc2faada6cc6139644f328bd36_amd64 as a component of Red Hat Offline Knowledge Portal 1.2.12; Red Hat build of Apache Camel 4.18.1.P1 for Spring Boot 3.5.16; Streams for Apache Kafka 3.2.1
    After
    log4j-jcl as a component of Red Hat Enterprise Linux 9; log4j-slf4j as a component of Red Hat Enterprise Linux 9; log4j.src as a component of Red Hat Enterprise Linux 9; log4j-layout-template-json as a component of Red Hat JBoss Enterprise Application Platform 7 · Fixed: Red Hat AMQ Broker 7.13.6; Red Hat AMQ Broker 7.14.1; Red Hat Data Grid 8.6.1; registry.redhat.io/offline-knowledge-portal/rhokp-rhel9@sha256:b26253f0a6c6b9e8c8458ecb07e79e9f87ff313491fffc31e342e32bce0a2b3e_arm64 as a component of Red Hat Offline Knowledge Portal 1.2.13; registry.redhat.io/offline-knowledge-portal/rhokp-rhel9@sha256:ec8b14b7a170b689a19cee7820888e81ddc3affc2faada6cc6139644f328bd36_amd64 as a component of Red Hat Offline Knowledge Portal 1.2.13; Red Hat build of Apache Camel 4.18.1.P1 for Spring Boot 3.5.16; Streams for Apache Kafka 3.2.1
    Red Hat Product Security ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    2.14.0 < 2.25.4; 3.0.0-alpha1 ≤ 3.0.0-beta3 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    2.14.0 < 2.25.4; 3.0.0-alpha1 ≤ 3.0.0-beta3 · Fixed: Before applying the update, back up your existing installation, including all applications, configuration files, databases and database settings. The References section of this erratum contains a download link (you must log in to download the update).
    Red Hat Product Security ↗
  3. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    Red Hat Product Security ↗
  4. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-34481 to remediation: access.redhat.com/CVE-2026-34481.
    Before
    remediation: access.redhat.com/CVE-2026-34481
    After
    remediation: access.redhat.com/CVE-2026-34481
    Red Hat Product Security ↗
  5. Affected versionsThe structured affected or fixed version information changed.
    Before
    log4j-layout-template-json as a component of Red Hat AMQ Broker 7; log4j-jcl as a component of Red Hat Enterprise Linux 9; log4j-slf4j as a component of Red Hat Enterprise Linux 9; log4j.src as a component of Red Hat Enterprise Linux 9 · Fixed: Red Hat Data Grid 8.6.1; registry.redhat.io/offline-knowledge-portal/rhokp-rhel9@sha256:b26253f0a6c6b9e8c8458ecb07e79e9f87ff313491fffc31e342e32bce0a2b3e_arm64 as a component of Red Hat Offline Knowledge Portal 1.2.12; registry.redhat.io/offline-knowledge-portal/rhokp-rhel9@sha256:ec8b14b7a170b689a19cee7820888e81ddc3affc2faada6cc6139644f328bd36_amd64 as a component of Red Hat Offline Knowledge Portal 1.2.12; Red Hat build of Apache Camel 4.18.1.P1 for Spring Boot 3.5.16; Streams for Apache Kafka 3.2.1
    After
    log4j-jcl as a component of Red Hat Enterprise Linux 9; log4j-slf4j as a component of Red Hat Enterprise Linux 9; log4j.src as a component of Red Hat Enterprise Linux 9; log4j-layout-template-json as a component of Red Hat JBoss Enterprise Application Platform 7 · Fixed: Red Hat AMQ Broker 7.13.6; Red Hat AMQ Broker 7.14.1; Red Hat Data Grid 8.6.1; registry.redhat.io/offline-knowledge-portal/rhokp-rhel9@sha256:b26253f0a6c6b9e8c8458ecb07e79e9f87ff313491fffc31e342e32bce0a2b3e_arm64 as a component of Red Hat Offline Knowledge Portal 1.2.12; registry.redhat.io/offline-knowledge-portal/rhokp-rhel9@sha256:ec8b14b7a170b689a19cee7820888e81ddc3affc2faada6cc6139644f328bd36_amd64 as a component of Red Hat Offline Knowledge Portal 1.2.12; Red Hat build of Apache Camel 4.18.1.P1 for Spring Boot 3.5.16; Streams for Apache Kafka 3.2.1
    Red Hat Product Security ↗
  6. Affected versionsThe structured affected or fixed version information changed.
    Before
    log4j-layout-template-json as a component of Red Hat AMQ Broker 7; log4j-jcl as a component of Red Hat Enterprise Linux 9; log4j-slf4j as a component of Red Hat Enterprise Linux 9; log4j.src as a component of Red Hat Enterprise Linux 9 · Fixed: Red Hat Data Grid 8.6.1; registry.redhat.io/offline-knowledge-portal/rhokp-rhel9@sha256:b26253f0a6c6b9e8c8458ecb07e79e9f87ff313491fffc31e342e32bce0a2b3e_arm64 as a component of Red Hat Offline Knowledge Portal 1.2.4; registry.redhat.io/offline-knowledge-portal/rhokp-rhel9@sha256:ec8b14b7a170b689a19cee7820888e81ddc3affc2faada6cc6139644f328bd36_amd64 as a component of Red Hat Offline Knowledge Portal 1.2.4; Red Hat build of Apache Camel 4.18.1.P1 for Spring Boot 3.5.16; Streams for Apache Kafka 3.2.1
    After
    log4j-layout-template-json as a component of Red Hat AMQ Broker 7; log4j-jcl as a component of Red Hat Enterprise Linux 9; log4j-slf4j as a component of Red Hat Enterprise Linux 9; log4j.src as a component of Red Hat Enterprise Linux 9 · Fixed: Red Hat Data Grid 8.6.1; registry.redhat.io/offline-knowledge-portal/rhokp-rhel9@sha256:b26253f0a6c6b9e8c8458ecb07e79e9f87ff313491fffc31e342e32bce0a2b3e_arm64 as a component of Red Hat Offline Knowledge Portal 1.2.12; registry.redhat.io/offline-knowledge-portal/rhokp-rhel9@sha256:ec8b14b7a170b689a19cee7820888e81ddc3affc2faada6cc6139644f328bd36_amd64 as a component of Red Hat Offline Knowledge Portal 1.2.12; Red Hat build of Apache Camel 4.18.1.P1 for Spring Boot 3.5.16; Streams for Apache Kafka 3.2.1
    Red Hat Product Security ↗
  7. Affected versionsThe structured affected or fixed version information changed.
    Before
    log4j-layout-template-json as a component of Red Hat AMQ Broker 7; log4j-jcl as a component of Red Hat Enterprise Linux 9; log4j-slf4j as a component of Red Hat Enterprise Linux 9; log4j.src as a component of Red Hat Enterprise Linux 9; log4j-layout-template-json as a component of Red Hat JBoss Enterprise Application Platform 7 · Fixed: Red Hat Data Grid 8.6.1; registry.redhat.io/offline-knowledge-portal/rhokp-rhel9@sha256:b26253f0a6c6b9e8c8458ecb07e79e9f87ff313491fffc31e342e32bce0a2b3e_arm64 as a component of Red Hat Offline Knowledge Portal 1.2.4; registry.redhat.io/offline-knowledge-portal/rhokp-rhel9@sha256:ec8b14b7a170b689a19cee7820888e81ddc3affc2faada6cc6139644f328bd36_amd64 as a component of Red Hat Offline Knowledge Portal 1.2.4; Red Hat build of Apache Camel 4.18.1.P1 for Spring Boot 3.5.16; Streams for Apache Kafka 3.2.1
    After
    log4j-layout-template-json as a component of Red Hat AMQ Broker 7; log4j-jcl as a component of Red Hat Enterprise Linux 9; log4j-slf4j as a component of Red Hat Enterprise Linux 9; log4j.src as a component of Red Hat Enterprise Linux 9 · Fixed: Red Hat Data Grid 8.6.1; registry.redhat.io/offline-knowledge-portal/rhokp-rhel9@sha256:b26253f0a6c6b9e8c8458ecb07e79e9f87ff313491fffc31e342e32bce0a2b3e_arm64 as a component of Red Hat Offline Knowledge Portal 1.2.4; registry.redhat.io/offline-knowledge-portal/rhokp-rhel9@sha256:ec8b14b7a170b689a19cee7820888e81ddc3affc2faada6cc6139644f328bd36_amd64 as a component of Red Hat Offline Knowledge Portal 1.2.4; Red Hat build of Apache Camel 4.18.1.P1 for Spring Boot 3.5.16; Streams for Apache Kafka 3.2.1
    Red Hat Product Security ↗
  8. Affected versionsThe structured affected or fixed version information changed.
    Before
    log4j-layout-template-json as a component of Red Hat AMQ Broker 7; log4j-jcl as a component of Red Hat Enterprise Linux 9; log4j-slf4j as a component of Red Hat Enterprise Linux 9; log4j.src as a component of Red Hat Enterprise Linux 9; log4j-layout-template-json as a component of Red Hat JBoss Enterprise Application Platform 7 · Fixed: Red Hat Data Grid 8.6.1; registry.redhat.io/offline-knowledge-portal/rhokp-rhel9@sha256:b26253f0a6c6b9e8c8458ecb07e79e9f87ff313491fffc31e342e32bce0a2b3e_arm64 as a component of Red Hat Offline Knowledge Portal 1.2.9; registry.redhat.io/offline-knowledge-portal/rhokp-rhel9@sha256:ec8b14b7a170b689a19cee7820888e81ddc3affc2faada6cc6139644f328bd36_amd64 as a component of Red Hat Offline Knowledge Portal 1.2.9; Red Hat build of Apache Camel 4.18.1.P1 for Spring Boot 3.5.16; Streams for Apache Kafka 3.2.1
    After
    log4j-layout-template-json as a component of Red Hat AMQ Broker 7; log4j-jcl as a component of Red Hat Enterprise Linux 9; log4j-slf4j as a component of Red Hat Enterprise Linux 9; log4j.src as a component of Red Hat Enterprise Linux 9; log4j-layout-template-json as a component of Red Hat JBoss Enterprise Application Platform 7 · Fixed: Red Hat Data Grid 8.6.1; registry.redhat.io/offline-knowledge-portal/rhokp-rhel9@sha256:b26253f0a6c6b9e8c8458ecb07e79e9f87ff313491fffc31e342e32bce0a2b3e_arm64 as a component of Red Hat Offline Knowledge Portal 1.2.4; registry.redhat.io/offline-knowledge-portal/rhokp-rhel9@sha256:ec8b14b7a170b689a19cee7820888e81ddc3affc2faada6cc6139644f328bd36_amd64 as a component of Red Hat Offline Knowledge Portal 1.2.4; Red Hat build of Apache Camel 4.18.1.P1 for Spring Boot 3.5.16; Streams for Apache Kafka 3.2.1
    Red Hat Product Security ↗
  9. Affected versionsThe structured affected or fixed version information changed.
    Before
    log4j-layout-template-json as a component of Red Hat AMQ Broker 7; log4j-jcl as a component of Red Hat Enterprise Linux 9; log4j-slf4j as a component of Red Hat Enterprise Linux 9; log4j.src as a component of Red Hat Enterprise Linux 9; log4j-layout-template-json as a component of Red Hat JBoss Enterprise Application Platform 7 · Fixed: Red Hat Data Grid 8.6.1; registry.redhat.io/offline-knowledge-portal/rhokp-rhel9@sha256:b26253f0a6c6b9e8c8458ecb07e79e9f87ff313491fffc31e342e32bce0a2b3e_arm64 as a component of Red Hat Offline Knowledge Portal 1.2.5; registry.redhat.io/offline-knowledge-portal/rhokp-rhel9@sha256:ec8b14b7a170b689a19cee7820888e81ddc3affc2faada6cc6139644f328bd36_amd64 as a component of Red Hat Offline Knowledge Portal 1.2.5; Red Hat build of Apache Camel 4.18.1.P1 for Spring Boot 3.5.16; Streams for Apache Kafka 3.2.1
    After
    log4j-layout-template-json as a component of Red Hat AMQ Broker 7; log4j-jcl as a component of Red Hat Enterprise Linux 9; log4j-slf4j as a component of Red Hat Enterprise Linux 9; log4j.src as a component of Red Hat Enterprise Linux 9; log4j-layout-template-json as a component of Red Hat JBoss Enterprise Application Platform 7 · Fixed: Red Hat Data Grid 8.6.1; registry.redhat.io/offline-knowledge-portal/rhokp-rhel9@sha256:b26253f0a6c6b9e8c8458ecb07e79e9f87ff313491fffc31e342e32bce0a2b3e_arm64 as a component of Red Hat Offline Knowledge Portal 1.2.9; registry.redhat.io/offline-knowledge-portal/rhokp-rhel9@sha256:ec8b14b7a170b689a19cee7820888e81ddc3affc2faada6cc6139644f328bd36_amd64 as a component of Red Hat Offline Knowledge Portal 1.2.9; Red Hat build of Apache Camel 4.18.1.P1 for Spring Boot 3.5.16; Streams for Apache Kafka 3.2.1
    Red Hat Product Security ↗
  10. Affected versionsThe structured affected or fixed version information changed.
    Before
    log4j-layout-template-json as a component of Red Hat AMQ Broker 7; log4j-jcl as a component of Red Hat Enterprise Linux 9; log4j-slf4j as a component of Red Hat Enterprise Linux 9; log4j.src as a component of Red Hat Enterprise Linux 9; log4j-layout-template-json as a component of Red Hat JBoss Enterprise Application Platform 7 · Fixed: Red Hat Data Grid 8.6.1; registry.redhat.io/offline-knowledge-portal/rhokp-rhel9@sha256:b26253f0a6c6b9e8c8458ecb07e79e9f87ff313491fffc31e342e32bce0a2b3e_arm64 as a component of Red Hat Offline Knowledge Portal 1.2.9; registry.redhat.io/offline-knowledge-portal/rhokp-rhel9@sha256:ec8b14b7a170b689a19cee7820888e81ddc3affc2faada6cc6139644f328bd36_amd64 as a component of Red Hat Offline Knowledge Portal 1.2.9; Red Hat build of Apache Camel 4.18.1.P1 for Spring Boot 3.5.16; Streams for Apache Kafka 3.2.1
    After
    log4j-layout-template-json as a component of Red Hat AMQ Broker 7; log4j-jcl as a component of Red Hat Enterprise Linux 9; log4j-slf4j as a component of Red Hat Enterprise Linux 9; log4j.src as a component of Red Hat Enterprise Linux 9; log4j-layout-template-json as a component of Red Hat JBoss Enterprise Application Platform 7 · Fixed: Red Hat Data Grid 8.6.1; registry.redhat.io/offline-knowledge-portal/rhokp-rhel9@sha256:b26253f0a6c6b9e8c8458ecb07e79e9f87ff313491fffc31e342e32bce0a2b3e_arm64 as a component of Red Hat Offline Knowledge Portal 1.2.5; registry.redhat.io/offline-knowledge-portal/rhokp-rhel9@sha256:ec8b14b7a170b689a19cee7820888e81ddc3affc2faada6cc6139644f328bd36_amd64 as a component of Red Hat Offline Knowledge Portal 1.2.5; Red Hat build of Apache Camel 4.18.1.P1 for Spring Boot 3.5.16; Streams for Apache Kafka 3.2.1
    Red Hat Product Security ↗
  11. Affected versionsThe structured affected or fixed version information changed.
    Before
    log4j-layout-template-json as a component of Red Hat AMQ Broker 7; log4j-jcl as a component of Red Hat Enterprise Linux 9; log4j-slf4j as a component of Red Hat Enterprise Linux 9; log4j.src as a component of Red Hat Enterprise Linux 9; log4j-layout-template-json as a component of Red Hat JBoss Enterprise Application Platform 7 · Fixed: Red Hat Data Grid 8.6.1; registry.redhat.io/offline-knowledge-portal/rhokp-rhel9@sha256:b26253f0a6c6b9e8c8458ecb07e79e9f87ff313491fffc31e342e32bce0a2b3e_arm64 as a component of Red Hat Offline Knowledge Portal 1.2.7; registry.redhat.io/offline-knowledge-portal/rhokp-rhel9@sha256:ec8b14b7a170b689a19cee7820888e81ddc3affc2faada6cc6139644f328bd36_amd64 as a component of Red Hat Offline Knowledge Portal 1.2.7; Red Hat build of Apache Camel 4.18.1.P1 for Spring Boot 3.5.16; Streams for Apache Kafka 3.2.1
    After
    log4j-layout-template-json as a component of Red Hat AMQ Broker 7; log4j-jcl as a component of Red Hat Enterprise Linux 9; log4j-slf4j as a component of Red Hat Enterprise Linux 9; log4j.src as a component of Red Hat Enterprise Linux 9; log4j-layout-template-json as a component of Red Hat JBoss Enterprise Application Platform 7 · Fixed: Red Hat Data Grid 8.6.1; registry.redhat.io/offline-knowledge-portal/rhokp-rhel9@sha256:b26253f0a6c6b9e8c8458ecb07e79e9f87ff313491fffc31e342e32bce0a2b3e_arm64 as a component of Red Hat Offline Knowledge Portal 1.2.9; registry.redhat.io/offline-knowledge-portal/rhokp-rhel9@sha256:ec8b14b7a170b689a19cee7820888e81ddc3affc2faada6cc6139644f328bd36_amd64 as a component of Red Hat Offline Knowledge Portal 1.2.9; Red Hat build of Apache Camel 4.18.1.P1 for Spring Boot 3.5.16; Streams for Apache Kafka 3.2.1
    Red Hat Product Security ↗
  12. Affected versionsThe structured affected or fixed version information changed.
    Before
    log4j-layout-template-json as a component of Red Hat AMQ Broker 7; log4j-jcl as a component of Red Hat Enterprise Linux 9; log4j-slf4j as a component of Red Hat Enterprise Linux 9; log4j.src as a component of Red Hat Enterprise Linux 9; log4j-layout-template-json as a component of Red Hat JBoss Enterprise Application Platform 7 · Fixed: Red Hat Data Grid 8.6.1; registry.redhat.io/offline-knowledge-portal/rhokp-rhel9@sha256:b26253f0a6c6b9e8c8458ecb07e79e9f87ff313491fffc31e342e32bce0a2b3e_arm64 as a component of Red Hat Offline Knowledge Portal 1.2.10; registry.redhat.io/offline-knowledge-portal/rhokp-rhel9@sha256:ec8b14b7a170b689a19cee7820888e81ddc3affc2faada6cc6139644f328bd36_amd64 as a component of Red Hat Offline Knowledge Portal 1.2.10; Red Hat build of Apache Camel 4.18.1.P1 for Spring Boot 3.5.16; Streams for Apache Kafka 3.2.1
    After
    log4j-layout-template-json as a component of Red Hat AMQ Broker 7; log4j-jcl as a component of Red Hat Enterprise Linux 9; log4j-slf4j as a component of Red Hat Enterprise Linux 9; log4j.src as a component of Red Hat Enterprise Linux 9; log4j-layout-template-json as a component of Red Hat JBoss Enterprise Application Platform 7 · Fixed: Red Hat Data Grid 8.6.1; registry.redhat.io/offline-knowledge-portal/rhokp-rhel9@sha256:b26253f0a6c6b9e8c8458ecb07e79e9f87ff313491fffc31e342e32bce0a2b3e_arm64 as a component of Red Hat Offline Knowledge Portal 1.2.7; registry.redhat.io/offline-knowledge-portal/rhokp-rhel9@sha256:ec8b14b7a170b689a19cee7820888e81ddc3affc2faada6cc6139644f328bd36_amd64 as a component of Red Hat Offline Knowledge Portal 1.2.7; Red Hat build of Apache Camel 4.18.1.P1 for Spring Boot 3.5.16; Streams for Apache Kafka 3.2.1
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release recorded from official guidance
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2026-21412↗Red Hat Product Security security advisory↗Vendor advisory↗Vendor advisory↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-34481 · cve.blacktree.nl