How severe is GHSA-rvpc-w57p-q95f?

GHSA-rvpc-w57p-q95f has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-rvpc-w57p-q95f?

GHSA-rvpc-w57p-q95f affects the following packages: org.wso2.transport.http:org.wso2.transport.http.netty (Maven). Ecosystems affected: Maven.

How do I fix GHSA-rvpc-w57p-q95f?

Update org.wso2.transport.http:org.wso2.transport.http.netty to 6.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rvpc-w57p-q95f is resolved across your whole dependency graph.

How do I detect GHSA-rvpc-w57p-q95f in my Maven dependencies?

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

How do I mitigate GHSA-rvpc-w57p-q95f if there is no patch (or I can't update yet)?

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.

Is GHSA-rvpc-w57p-q95f actively exploited in the wild?

No public exploit code has been indexed for GHSA-rvpc-w57p-q95f 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-rvpc-w57p-q95f?

GHSA-rvpc-w57p-q95f has an EPSS (Exploit Prediction Scoring System) score of 1.3%, placing it in the 69th 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.

When was GHSA-rvpc-w57p-q95f published, and has it been updated?

GHSA-rvpc-w57p-q95f was published on February 9, 2022 and was last updated on September 10, 2026. 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

MEDIUM severity

HTTP Response Splitting in WSO2 transport-httpGHSA-rvpc-w57p-q95f

MEDIUM

GHSA-rvpc-w57p-q95f is a medium-severity (CVSS 6.5) vulnerability in org.wso2.transport.http:org.wso2.transport.http.netty. A fix is available for org.wso2.transport.http:org.wso2.transport.http.netty — see the affected versions and patch details below.

Also known asCVE-2019-10797SNYK-JAVA-ORGWSO2TRANSPORTHTTP-548944

Published

Feb 9, 2022

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs69th percentile — riskier than 69% of all scored CVEsHighest risk

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

How urgent is this, really

GHSA-rvpc-w57p-q95f by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

☕org.wso2.transport.http:org.wso2.transport.http.netty

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

Netty in WSO2 transport-http before v6.3.1 is vulnerable to HTTP Response Splitting due to HTTP Header validation being disabled.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.wso2.transport.http:org.wso2.transport.http.netty`	all versions	6.3.1`org.wso2.transport.http:org.wso2.transport.http.netty:6.3.1`

Affected Products

1 product · 1 configurations

Application

transport-httpwso2

< 6.3.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.wso2.transport.http:org.wso2.transport.http.netty, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.wso2.transport.http:org.wso2.transport.http.netty to 6.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rvpc-w57p-q95f is resolved across your whole dependency graph.
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

Netty in WSO2 transport-http before v6.3.1 is vulnerable to HTTP Response Splitting due to HTTP Header validation being disabled.

O3 Security · Impact-Aware SCA

Is GHSA-rvpc-w57p-q95f in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works