How severe is CVE-2019-17195?

CVE-2019-17195 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2019-17195?

CVE-2019-17195 affects the following packages: com.nimbusds:nimbus-jose-jwt (Maven). Ecosystems affected: Maven.

How do I fix CVE-2019-17195?

Update com.nimbusds:nimbus-jose-jwt to 7.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-17195 is resolved across your whole dependency graph.

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

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

How do I mitigate CVE-2019-17195 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

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

Yes. There are 2 known exploit references for CVE-2019-17195, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2019-17195?

CVE-2019-17195 has an EPSS (Exploit Prediction Scoring System) score of 11.1%, placing it in the 96th 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 warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2019-17195?

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

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

CVE-2019-17195 was published on October 15, 2019 and was last updated on October 24, 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

CRITICAL severity

CVE-2019-17195 — nimbus-jose-jwt

CRITICAL

CVE-2019-17195 is a critical-severity (CVSS 9.8) CWE-755 vulnerability in com.nimbusds:nimbus-jose-jwt. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for com.nimbusds:nimbus-jose-jwt — see the affected versions and patch details below.

Improper Check for Unusual or Exceptional Conditions in Connect2id Nimbus JOSE+JWT

Also known asGHSA-f6vf-pq8c-69m4

Published

Oct 15, 2019

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

2 known

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

EPSS Exploitation Probability

via FIRST.org ↗

11.1%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs96th percentile — riskier than 96% of all scored CVEsHighest risk

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.nimbusds:nimbus-jose-jwt

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

Connect2id Nimbus JOSE+JWT before v7.9 can throw various uncaught exceptions while parsing a JWT, which could result in an application crash (potential information disclosure) or a potential authentication bypass.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.nimbusds:nimbus-jose-jwt`	all versions	7.9`com.nimbusds:nimbus-jose-jwt:7.9`

Affected Products

15 products · 18 configurations

Application

hadoopapache

1 version

3.2.1

Application

nimbus jose\+jwtconnect2id

< 7.9

range

Application

communications cloud native core security edge protection proxyoracle

1 version

1.7.0

Application

communications pricing design centeroracle

1 version

12.0.0.3.0

Application

data integratororacle

1 version

12.2.1.4.0

Application

enterprise manager base platformoracle

1 version

13.4.0.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Connect2id Nimbus JOSE+JWT before v7.9 can throw various uncaught except…

github.comGithubFeb 2021

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.nimbusds:nimbus-jose-jwt, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.nimbusds:nimbus-jose-jwt to 7.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-17195 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

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

In Red Hat Virtualization 4.2, nimbus-jose-jwt was bundled in the rhvm-dependencies package. In Red Hat Virtualization 4.3, nimbus-jose-jwt was made available as a separate package and no longer bundled in rhvm-dependencies. Thus, rhvm-dependencies only contained this vulnerability in the 4.2 EUS stream, the 4.3…

Product	Fixed in	Advisory
Red Hat Virtualization 4 for Red Hat Enterprise Linux 7	`apache-commons-beanutils-0:1.8.3-15.el7_7`	RHSA-2020:1308

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2019-17195 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2019-17195 — nimbus-jose-jwt

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2019-17195 in your dependencies?