2843 matches found
Important: Red Hat Security Advisory: Streams for Apache Kafka 3.2.1 release and security update
Streams for Apache Kafka 3.2.1 is now available from the Red Hat Customer Portal. Red Hat Product Security has rated this update as having a security impact of Moderate. A Common Vulnerability Scoring System CVSS base score, which gives a detailed severity rating, is available for each...
org.apache.logging.log4j/log4j-core: Apache Log4j Core: Log injection via CRLF sequences due to configuration attribute renames
A flaw was found in Apache Log4j Core. This vulnerability allows for log injection through the use of Carriage Return Line Feed CRLF sequences. This occurs because security-related configuration attributes were silently renamed, impacting users who directly configure Rfc5424Layout with stream-bas...
Security Bulletin:Vulnerability in Log4j affects IBM Netezza Appliance
Summary The Log4j package is used by IBM Netezza Appliance. IBM Netezza Appliance has addressed the applicable CVE CVE-2026-49844 Vulnerability Details CVEID:CVE-2026-49844 DESCRIPTION: Improper encoding of non-finite floating-point values during MapMessage JSON serialization in Apache Log4j API...
Security Bulletin: due to the use of Apache Log4j, IBM Transformation Extender Advanced is vulnerable to hostname verification bypass and log injection via CRLF sequences
Summary Apache Log4j is used by IBM Transformation Extender Advanced also known as IBM Standards Processing Engine as part of common utility helpers. Apache Log4j has been updated to address CVE-2026-34477 which causes hostname verification bypass and CVE-2026-34478 which causes log injection via...
Security Bulletin: IBM InfoSphere Information Server is affected by multiple vulnerabilities in Apache Log4j
Summary Multiple vulnerabilities in Apache Log4j that is used by InfoSphere Information Server were addressed. Vulnerability Details CVEID:CVE-2026-34477 DESCRIPTION: The fix for CVE-2025-68161 https://logging.apache.org/security.htmlCVE-2025-68161 was incomplete: it addressed hostname verificati...
CLSA-2026-1785727932 TuxCare security update for org.apache.logging.log4j (3 CVEs)
TuxCare rebuilt 33 org.apache.logging.log4j packages to address 3 CVEs. Fixed in 2.17.2-tuxcare.2...
CLSA-2026-1785380784 TuxCare security update for org.apache.logging.log4j (1 CVE)
TuxCare rebuilt 32 org.apache.logging.log4j packages to address 1 CVE. Fixed in 2.22.1-tuxcare.3...
CLSA-2026-1784683011 TuxCare security update for org.apache.logging.log4j (2 CVEs)
TuxCare rebuilt 30 org.apache.logging.log4j packages to address 2 CVEs. Fixed in 2.24.3-tuxcare.1...
CLSA-2026-1784769542 TuxCare security update for org.apache.logging.log4j (2 CVEs)
TuxCare rebuilt 34 org.apache.logging.log4j packages to address 2 CVEs. Fixed in 2.18.0-tuxcare.1...
CLSA-2026-1780447835 TuxCare security update for org.apache.logging.log4j (3 CVEs)
TuxCare rebuilt 32 org.apache.logging.log4j packages to address 3 CVEs. Fixed in 2.22.1-tuxcare.1...
CLSA-2025-1751328204 TuxCare security update for log4j:log4j (6 CVEs)
TuxCare rebuilt log4j:log4j to address 6 CVEs. Fixed in 1.2.17.tuxcare.1...
Improper Encoding Or Escaping Of Output
Apache Log4j API is vulnerable to Improper Encoding or Escaping of Output. The vulnerability is due to improper encoding of non-finite floating-point values during MapMessage JSON serialization, which allows an attacker to inject NaN or Infinity values that produce malformed JSON and disrupt...
Security Bulletin: IBM Storage Protect Data Protection for Virtual Environments uses Apache Log4j version that is vulnerable to log injection via CRLF sequences due to undocumented renames of security-relevant configuration attributes ( CVE-2026-34478)
Summary IBM Storage Protect Data Protection for Virtual Environments uses Apache Log4j version that is vulnerable to log injection via CRLF sequences due to undocumented renames of security-relevant configuration attributes. This issue has been fixed in this release by incorporating the Apache...
Security Bulletin: IBM Db2 Developer Extension is affected by vulnerability in log4j core (CVE-2026-34477, CVE-2026-34478)
Summary IBM Db2 Developer Extension is affected by vulnerability in log4j core CVE-2026-34477, CVE-2026-34478 Vulnerability Details CVEID:CVE-2026-34477 DESCRIPTION: The fix for CVE-2025-68161 https://logging.apache.org/security.htmlCVE-2025-68161 was incomplete: it addressed hostname verificatio...
ROOT-APP-MAVEN-CVE-2026-34477 CVE-2026-34477 in io.root.org.apache.logging.log4j:log4j-core - Patched by Root
Root has patched CVE-2026-34477 in the io.root.org.apache.logging.log4j:log4j-core package for Root:Maven. Multiple fixed versions available...
ROOT-APP-MAVEN-CVE-2026-34479 CVE-2026-34479 in io.root.org.apache.logging.log4j:log4j-1.2-api - Patched by Root
Root has patched CVE-2026-34479 in the io.root.org.apache.logging.log4j:log4j-1.2-api package for Root:Maven. Multiple fixed versions available...
ROOT-APP-MAVEN-CVE-2026-34481 CVE-2026-34481 in io.root.org.apache.logging.log4j:log4j-layout-template-json - Patched by Root
Root has patched CVE-2026-34481 in the io.root.org.apache.logging.log4j:log4j-layout-template-json package for Root:Maven. Multiple fixed versions available...
Security Bulletin: IBM Engineering Systems Design Rhapsody TestConductor was affected by Vulnerability in log4j
Summary Security Bulletin: IBM Engineering Systems Design Rhapsody TestConductor was affected by Vulnerability in log4j. Even though Rhapsody risk impact was low we have addressed these Vulnerability on our latest iFIx for all versions. Vulnerability Details CVEID:CVE-2026-34477 DESCRIPTION: The...
The vulnerability of the verifyHostName configuration parameter in the Apache Log4j Core library allows a attacker to perform a “man-in-the-middle” attack.
The vulnerability of the verifyHostName configuration parameter in the Apache Log4j Core logging library is related to errors in the certificate validation process. Exploiting this vulnerability allows a malicious actor to carry out a “man-in-the-middle” attack remotely...
CVE-2026-49844
A flaw was found in Apache Log4j API. This vulnerability occurs due to improper encoding of non-finite floating-point values during JSON serialization of MapMessages, leading to invalid JSON output. An attacker who can supply a non-finite value can exploit this to cause the affected logging layou...