CVE-2022-32096

HIGHNVD 7.57.5—

7.5

Rhonabwy before v1.1.5 was discovered to contain a buffer overflow via the component r_jwe_aesgcm_key_unwrap. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted JWE token.

CVSS v3: 7.5
EG Score: 7.5(medium)
EPSS: 68.9%
KEV: Not listed

Published

July 13, 2022

Last Modified

November 21, 2024

References (4)

cve@mitrehttps://github.com/babelouest/rhonabwy/
cve@mitrehttps://github.com/babelouest/rhonabwy/commit/b4c2923a1ba4fabf9b55a89244127e153a3e549b
af854a3a-2127-422b-91ae-364da2661108https://github.com/babelouest/rhonabwy/
af854a3a-2127-422b-91ae-364da2661108https://github.com/babelouest/rhonabwy/commit/b4c2923a1ba4fabf9b55a89244127e153a3e549b

Weakness Classification(1)

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

CWE-120Buffer Copy without Checking Size (Classic Buffer Overflow)

Data Freshness Timeline

(refreshed 14× in last 7d / 20× 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-06-05 06:09 UTCepss_batch
2026-06-05 06:09 UTCepss_batch
2026-06-04 13:11 UTCepss_batch
2026-06-04 13:11 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-29 13:43 UTCepss_batch
2026-05-29 13:42 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-27 13:39 UTCepss_batch

Frequently asked(5)

What is CVE-2022-32096?

CVE-2022-32096 is a high vulnerability published on July 13, 2022. Rhonabwy before v1.1.5 was discovered to contain a buffer overflow via the component rjweaesgcmkeyunwrap. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted JWE token.

When was CVE-2022-32096 disclosed?

CVE-2022-32096 was first published in the National Vulnerability Database on July 13, 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-32096 actively exploited?

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

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

CVE-2022-32096 has a CVSS v3 base score of 7.5 (NVD).

How do I remediate CVE-2022-32096?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-32096, 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-32096

Explore →

Is Your Infrastructure Affected by CVE-2022-32096?

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

Start Free Scan →Browse All CVEs

CVE-2022-32096

📅 Published

🔄 Last Modified

🔗 References (4)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2022-32096?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (4)

Frequently asked(5)

Related CVEs(same CWE)