How severe is CVE-2006-0743?

No CVSS score has been assigned to CVE-2006-0743 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2006-0743?

CVE-2006-0743 affects the following packages: log4net (NuGet). Ecosystems affected: NuGet.

How do I fix CVE-2006-0743?

Update log4net to 1.2.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2006-0743 is resolved across your whole dependency graph.

How do I detect CVE-2006-0743 in my NuGet dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for log4net, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2006-0743 if there is no patch (or I can't update yet)?

Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Is CVE-2006-0743 actively exploited in the wild?

No public exploit code has been indexed for CVE-2006-0743 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2006-0743?

CVE-2006-0743 has an EPSS (Exploit Prediction Scoring System) score of 6.4%, placing it in the 94th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2006-0743?

CVE-2006-0743 is classified as CWE-134 (CWE-134). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2006-0743 published, and has it been updated?

CVE-2006-0743 was published on May 1, 2022 and was last updated on February 9, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

.NET NuGet

Not in CISA KEV

CVE-2006-0743 — log4net

Fix: apache/logging-log4net@ea3faab

CVE-2006-0743 is a CWE-134 vulnerability in log4net. A fix is available for log4net — see the affected versions and patch details below.

Apache log4net format string vulnerability causes DoS

Published

May 1, 2022

Updated

Feb 9, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 2, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

6.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs94th percentile — riskier than 94% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

.NETlog4net

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.

Description

Format string vulnerability in LocalSyslogAppender in Apache log4net 1.2.9 might allow remote attackers to cause a denial of service (memory corruption and termination) via unknown vectors.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
.NETNuGet	`log4net`	all versions	1.2.10`dotnet add package log4net --version 1.2.10`

Affected Products

1 product · 1 configurations

Application

log4netapache

1 version

1.2.9_beta

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for log4net, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update log4net to 1.2.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2006-0743 is resolved across your whole dependency graph.
Workarounds
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Frequently Asked Questions

Format string vulnerability in LocalSyslogAppender in Apache log4net 1.2.9 might allow remote attackers to cause a denial of service (memory corruption and termination) via unknown vectors.