How severe is GHSA-gw85-4gmf-m7rh?

No CVSS score has been assigned to GHSA-gw85-4gmf-m7rh yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-gw85-4gmf-m7rh?

GHSA-gw85-4gmf-m7rh affects the following packages: org.apache.httpcomponents:httpclient (Maven). Ecosystems affected: Maven.

How do I fix GHSA-gw85-4gmf-m7rh?

Update org.apache.httpcomponents:httpclient to 4.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gw85-4gmf-m7rh is resolved across your whole dependency graph.

How do I detect GHSA-gw85-4gmf-m7rh in my Maven dependencies?

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

How do I mitigate GHSA-gw85-4gmf-m7rh if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is GHSA-gw85-4gmf-m7rh actively exploited in the wild?

No public exploit code has been indexed for GHSA-gw85-4gmf-m7rh 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 GHSA-gw85-4gmf-m7rh?

GHSA-gw85-4gmf-m7rh has an EPSS (Exploit Prediction Scoring System) score of 6.7%, 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 GHSA-gw85-4gmf-m7rh?

GHSA-gw85-4gmf-m7rh is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-gw85-4gmf-m7rh published, and has it been updated?

GHSA-gw85-4gmf-m7rh was published on May 17, 2022 and was last updated on December 3, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

Exposure of Sensitive Information to an Unauthorized Actor in Apache HttpClientGHSA-gw85-4gmf-m7rh

Fix: apache/httpcomponents-client@a572756

GHSA-gw85-4gmf-m7rh is a Information Exposure vulnerability in org.apache.httpcomponents:httpclient. A fix is available for org.apache.httpcomponents:httpclient — see the affected versions and patch details below.

Also known asCVE-2011-1498

Published

May 17, 2022

Updated

Dec 3, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

6.7%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

☕org.apache.httpcomponents:httpclient

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

Apache HttpClient 4.x before 4.1.1 in Apache HttpComponents, when used with an authenticating proxy server, sends the Proxy-Authorization header to the origin server, which allows remote web servers to obtain sensitive information by logging this header.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.httpcomponents:httpclient`	≥ 4.0.0&&< 4.1.1	4.1.1`org.apache.httpcomponents:httpclient:4.1.1`

Affected Products

1 product · 12 configurations

Application

httpclientapache

3 versions

4.04.0.14.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.httpcomponents:httpclient, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.httpcomponents:httpclient to 4.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gw85-4gmf-m7rh is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-gw85-4gmf-m7rh in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works