Verified80% confidenceFactExact time
The Log4j vulnerability was discovered in 2021, designated CVE-2021-44228, and is a remote code execution vulnerability affecting this widely used Java logging library.
8
Sources
80%
Confidence
Long-term
Relevance
7/11/2026
First Seen
Sources
Decoding the Government Software Security Executive Order: New Supply Chain Compliance and SBOM Requirements
hackernewshackernews7/9/2026
Related Claims
UnverifiedThe Log4j vulnerability (CVE-2021-44228) allows attackers to trigger a JNDI lookup via a crafted string to achieve unauthenticated remote code execution.80% similarVerifiedCVE-2021-44228 is the well-known Log4Shell vulnerability77% similarUnverifiedLog4Shell漏洞（CVE-2021-44228）被安全研究人员评为CVSS满分10.0，利用门槛极低，仅需在日志中注入一段JNDI查询字符串76% similarUnverifiedThe Log4Shell vulnerability originated in a logging library maintained by volunteers and affected billions of devices worldwide.68% similarUnverifiedThe Heartbleed vulnerability in OpenSSL and the Log4Shell vulnerability in Log4j exposed systemic issues of insufficient maintenance resources for critical open-source projects.65% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/476621API
curl https://kongchang.com/api/v1/knowledge/claims/476621MCP
get_claim(id=476621)