NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
MEDIUM severity

CVE-2022-32531 — bookkeeper-common

MEDIUM

CVE-2022-32531 is a medium-severity (CVSS 5.9) CWE-295 vulnerability in org.apache.bookkeeper:bookkeeper-common. A fix is available for org.apache.bookkeeper:bookkeeper-common — see the affected versions and patch details below.

Apache BookKeeper: Java Client Uses Connection to Host that Failed Hostname Verification

Also known asGHSA-gxq5-79m2-gvvqPYSEC-2022-43060
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2022-32531.

EPSS Exploitation Probability

via FIRST.org ↗
1.1%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs66th percentile — riskier than 66% of all scored CVEsHighest risk
0.30%0.73%1.16%1.59%0.8%1.1%May 26Sep 26Nov 26

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected
☕org.apache.bookkeeper:bookkeeper-common☕org.apache.bookkeeper:bookkeeper-common

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

Description

The Apache Bookkeeper Java Client (before 4.14.6 and also 4.15.0) does not close the connection to the bookkeeper server when TLS hostname verification fails. This leaves the bookkeeper client vulnerable to a man in the middle attack.

The problem affects BookKeeper client prior to versions 4.14.6 and 4.15.1.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.apache.bookkeeper:bookkeeper-commonall versions4.14.6org.apache.bookkeeper:bookkeeper-common:4.14.6
☕Mavenorg.apache.bookkeeper:bookkeeper-common≥ 4.15.0&&< 4.15.14.15.1org.apache.bookkeeper:bookkeeper-common:4.15.1

Affected Products

1 product · 3 configurations
Application
bookkeeperapache
< 4.14.6
1 version
4.15.0

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update org.apache.bookkeeper:bookkeeper-common to 4.14.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-32531 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

The Apache Bookkeeper Java Client (before 4.14.6 and also 4.15.0) does not close the connection to the bookkeeper server when TLS hostname verification fails. This leaves the bookkeeper client vulnerable to a man in the middle attack. The problem affects BookKeeper client prior to versions 4.14.6 and 4.15.1.
O3 Security · Impact-Aware SCA

Is CVE-2022-32531 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2022-32531: bookkeeper-common — Fixed in 4.14.6