Unverified60% confidenceFactExact time
The Log4j vulnerability (CVE-2021-44228) allows attackers to trigger a JNDI lookup via a crafted string to achieve unauthenticated remote code execution.
2
Sources
60%
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
VerifiedThe Log4j vulnerability was discovered in 2021, designated CVE-2021-44228, and is a remote code execution vulnerability affecting this widely used Java logging library.80% similarUnverifiedLog4Shell漏洞（CVE-2021-44228）被安全研究人员评为CVSS满分10.0，利用门槛极低，仅需在日志中注入一段JNDI查询字符串77% similarUnverifiedAttackers may be able to exploit this PHP vulnerability to execute code remotely without authentication.76% similarVerifiedCVE-2026-55040 allows an attacker to achieve remote code execution as an arbitrary user without authentication.75% similarUnverifiedCVE-2020-9906 is a remotely exploitable memory corruption vulnerability that allows an attacker within physical proximity to achieve code execution without any user interaction.74% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/484128API
curl https://kongchang.com/api/v1/knowledge/claims/484128MCP
get_claim(id=484128)