How severe is CVE-2019-0205?

CVE-2019-0205 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2019-0205?

CVE-2019-0205 affects the following packages: org.apache.thrift:libthrift (Maven). Ecosystems affected: Maven.

How do I fix CVE-2019-0205?

Update org.apache.thrift:libthrift to 0.13.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-0205 is resolved across your whole dependency graph.

How do I detect CVE-2019-0205 in my Maven dependencies?

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

How do I mitigate CVE-2019-0205 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.

How does O3 Security protect against CVE-2019-0205?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2019-0205 can be triaged on real exposure rather than presence alone.

Is CVE-2019-0205 actively exploited in the wild?

No public exploit code has been indexed for CVE-2019-0205 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 CVE-2019-0205?

CVE-2019-0205 has an EPSS (Exploit Prediction Scoring System) score of 9.2%, placing it in the 95th 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 CVE-2019-0205?

CVE-2019-0205 is classified as CWE-835 (CWE-835). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2019-0205 published, and has it been updated?

CVE-2019-0205 was published on October 29, 2019 and was last updated on July 8, 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

HIGH severity

CVE-2019-0205 — libthrift

HIGH

CVE-2019-0205 is a high-severity (CVSS 7.5) CWE-835 vulnerability in org.apache.thrift:libthrift. A fix is available for org.apache.thrift:libthrift — see the affected versions and patch details below.

Loop with Unreachable Exit Condition in Apache Thrift

Also known asGHSA-rj7p-rfgp-852x

Published

Oct 29, 2019

Updated

Jul 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

9.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs95th percentile — riskier than 95% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

CVE-2019-0205 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 378,156 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

1 pkg affected

☕org.apache.thrift:libthrift

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

In Apache Thrift all versions up to and including 0.12.0, a server or client may run into an endless loop when feed with specific input data. Because the issue had already been partially fixed in version 0.11.0, depending on the installed version it affects only certain language bindings.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.thrift:libthrift`	all versions	0.13.0`org.apache.thrift:libthrift:0.13.0`

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.thrift:libthrift, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.thrift:libthrift to 0.13.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-0205 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2019-0205 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2019-0205. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Red Hat OpenStack Platform ships OpenDaylight, which contains a vulnerable version of libthrift. However, OpenDaylight does not expose libthrift in a vulnerable way, lowering the impact of the vulnerability for OpenDaylight. As such, Red Hat will not be providing a fix for OpenDaylight at this time. The thrift package…

Product	Fixed in	Advisory
EAP-CD 19 Tech Preview	`libthrift`	RHSA-2020:2333
Red Hat Data Grid 7.3.6	`libthrift`	RHSA-2020:2321
Red Hat Fuse 7.8.0	`libthrift`	RHSA-2020:5568
Red Hat JBoss EAP 7	`libthrift`	RHSA-2020:2515
Red Hat JBoss EAP 7.2	`libthrift`	RHSA-2020:0811
Red Hat JBoss Enterprise Application Platform 7	`libthrift`	RHSA-2020:0961
Red Hat JBoss Enterprise Application Platform 7.2 for RHEL 6	`eap7-activemq-artemis-0:2.9.0-2.redhat_00009.1.el6eap`	RHSA-2020:0804
Red Hat JBoss Enterprise Application Platform 7.2 for RHEL 7	`eap7-activemq-artemis-0:2.9.0-2.redhat_00009.1.el7eap`	RHSA-2020:0805

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2019-0205 in your dependencies?

O3 Security finds CVE-2019-0205 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works