CVE-2019-1010161: perl-CRYPT-JWT 0.022 and earlier is affected by: Incorrect Access Control

Q: How do I fix CVE-2019-1010161?

perl-crypt-jwt: upgrade to newer than 0.022. Exact commands for each OS are on this page.

Q: Is CVE-2019-1010161 being exploited?

CVE-2019-1010161 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2019-1010161 affect?

CVE-2019-1010161 affects perl-crypt-jwt. Severity is critical (CVSS 9.8). perl-CRYPT-JWT 0.022 and earlier is affected by: Incorrect Access Control. The impact is: bypass authentication. The component is: JWT.pm for JWT security token, line 614 in _decode_jws(). The attack vector is: network connectivity(crafting

Q: How urgent is CVE-2019-1010161?

Priority 56/100. Critical severity; Remotely exploitable, no login, no user action

This month

CRITICAL 9.8REMOTEUPGRADE

CVE-2019-1010161 is a critical-severity flaw (CVSS 9.8) affecting perl-crypt-jwt. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

perl-CRYPT-JWT 0.022 and earlier is affected by: Incorrect Access Control. The impact is: bypass authentication. The component is: JWT.pm for JWT security token, line 614 in _decode_jws(). The attack vector is: network connectivity(crafting user-controlled input to bypass authentication). The fixed version is: 0.023.

Why this priority

Critical severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.1% (top 34%)
CISA exploited list	No
Weakness	CWE-347
Published	2019-07-25
Last modified	2026-06-17

Publisher (CNA): DWF · Vendor: perl-crypt-jwt project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2019-07-25 14:15 UTCPublished CVE record published
2026-06-17 02:09 UTCUpdated Record last modified

perl-crypt-jwt project perl-crypt-jwt UPGRADE

Affected: <= 0.022

Fixed in: newer than 0.022

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy perl-crypt-jwt || rpm -q perl-crypt-jwt || perl-crypt-jwt --version

2. UPGRADE to newer than 0.022 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade perl-crypt-jwt

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade perl-crypt-jwt

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2019-1010161?

perl-crypt-jwt: upgrade to newer than 0.022. Exact commands for each OS are on this page.

Is CVE-2019-1010161 being exploited?

CVE-2019-1010161 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2019-1010161 affect?

CVE-2019-1010161 affects perl-crypt-jwt. Severity is critical (CVSS 9.8). perl-CRYPT-JWT 0.022 and earlier is affected by: Incorrect Access Control. The impact is: bypass authentication. The component is: JWT.pm for JWT security token, line 614 in _decode_jws(). The attack vector is: network connectivity(crafting

How urgent is CVE-2019-1010161?

Priority 56/100. Critical severity; Remotely exploitable, no login, no user action

Software pages

Perl vulnerabilities

References

← Back to latest CVEs