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

Play Framework Inadequate Encryption Strength vulnerabilityGHSA-442g-gcg6-mhm4

HIGH

GHSA-442g-gcg6-mhm4 is a high-severity (CVSS 7.5) CWE-326 vulnerability in com.typesafe.play:play-ws_2.12. A fix is available for com.typesafe.play:play-ws_2.12 — see the affected versions and patch details below.

Also known asCVE-2019-17598
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 12, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.7%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs54th percentile — riskier than 54% of all scored CVEsHighest risk
0.00%0.40%0.80%1.20%0.1%0.7%0.7%0.7%Jun 26Nov 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

1 pkg affected
☕com.typesafe.play:play-ws_2.12

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

An issue was discovered in Lightbend Play Framework 2.5.x through 2.6.23. When configured to make requests using an authenticated HTTP proxy, play-ws may sometimes, typically under high load, when connecting to a target host using https, expose the proxy credentials to the target host.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
☕Mavencom.typesafe.play:play-ws_2.12≥ 2.5.0&&< 2.6.242.6.24com.typesafe.play:play-ws_2.12:2.6.24

Affected Products

1 product · 2 configurations
Application
play frameworklightbend
≥ 2.6.0 && ≤ 2.6.23
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update com.typesafe.play:play-ws_2.12 to 2.6.24 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-442g-gcg6-mhm4 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

An issue was discovered in Lightbend Play Framework 2.5.x through 2.6.23. When configured to make requests using an authenticated HTTP proxy, play-ws may sometimes, typically under high load, when connecting to a target host using https, expose the proxy credentials to the target host.
O3 Security · Impact-Aware SCA

Is GHSA-442g-gcg6-mhm4 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
Play Framework Inadequate Encryption Strength…