CVE-2022-32549

MEDIUMNVD 5.35.3—

5.3

Apache Sling Commons Log <= 5.4.0 and Apache Sling API <= 2.25.0 are vulnerable to log injection. The ability to forge logs may allow an attacker to cover tracks by injecting fake logs and potentially corrupt log files.

CVSS v3: 5.3
EG Score: 5.3(medium)
EPSS: 86.5%
KEV: Not listed

Published

June 22, 2022

Last Modified

November 21, 2024

References (2)

security@apachehttps://lists.apache.org/thread/7z6h3806mwcov5kx6l96pq839sn0po1v
af854a3a-2127-422b-91ae-364da2661108https://lists.apache.org/thread/7z6h3806mwcov5kx6l96pq839sn0po1v

Patch Availability(2)

Vendor / Ecosystem	Fixed in / Patch	Released	Source
maven	org.apache.sling:org.apache.sling.api	—	ghsa
maven	org.apache.sling:org.apache.sling.commons.log	—	ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 1 ecosystem)

Maven(2)

Package	Vulnerable range	Fixed in	Dependents
org.apache.sling:org.apache.sling.api	2.0.2-incubator ... 2.9.0 (35 versions)	—	—
org.apache.sling:org.apache.sling.commons.log	2.0.2-incubator ... 5.4.0 (24 versions)	—	—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 9× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-05-27 13:39 UTCepss_batch
2026-05-27 13:39 UTCepss_batch
2026-05-26 13:43 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-25 20:04 UTCEG score recompute
2026-05-25 20:04 UTCGHSA enrichment
2026-05-24 16:51 UTCepss_batch

Frequently asked(5)

What is CVE-2022-32549?

CVE-2022-32549 is a medium vulnerability published on June 22, 2022. Apache Sling Commons Log <= 5.4.0 and Apache Sling API <= 2.25.0 are vulnerable to log injection. The ability to forge logs may allow an attacker to cover tracks by injecting fake logs and potentially corrupt log files.

When was CVE-2022-32549 disclosed?

CVE-2022-32549 was first published in the National Vulnerability Database on June 22, 2022, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2022-32549 actively exploited?

CVE-2022-32549 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 86.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2022-32549?

CVE-2022-32549 has a CVSS v3 base score of 5.3 (NVD).

How do I remediate CVE-2022-32549?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-32549, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-32549

Explore →

Is Your Infrastructure Affected by CVE-2022-32549?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs