CVE-2024-33531

HIGHNVD 8.18.1—Elevated

8.1

cdbattags lua-resty-jwt 0.2.3 allows attackers to bypass all JWT-parsing signature checks by crafting a JWT with an enc header with the value A256GCM.

CVSS v3: 8.1
EG Score: 8.1(medium)
EPSS: 27.9%
KEV: Not listed

Published

April 24, 2024

Last Modified

April 15, 2026

References (6)

cve@mitrehttps://github.com/cdbattags/lua-resty-jwt/commit/d1558e2afefe868fea1e7e9a4b04ea94ab678a85
cve@mitrehttps://github.com/cdbattags/lua-resty-jwt/issues/61
cve@mitrehttps://insinuator.net/2023/10/lua-resty-jwt-authentication-bypass/
af854a3a-2127-422b-91ae-364da2661108https://github.com/cdbattags/lua-resty-jwt/commit/d1558e2afefe868fea1e7e9a4b04ea94ab678a85
af854a3a-2127-422b-91ae-364da2661108https://github.com/cdbattags/lua-resty-jwt/issues/61
af854a3a-2127-422b-91ae-364da2661108https://insinuator.net/2023/10/lua-resty-jwt-authentication-bypass/

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-290Authentication Bypass by Spoofing

Data Freshness Timeline

(refreshed 14× in last 7d / 20× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-02 20:12 UTCepss_batch
2026-06-02 20:12 UTCepss_batch
2026-06-01 13:51 UTCepss_batch
2026-06-01 13:51 UTCepss_batch
2026-06-01 13:51 UTCepss_batch
2026-05-31 22:30 UTCepss_batch
2026-05-31 22:30 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-29 13:43 UTCepss_batch
2026-05-29 13:43 UTCepss_batch
2026-05-28 13:44 UTCepss_batch
2026-05-28 13:44 UTCepss_batch
2026-05-28 13:44 UTCepss_batch
2026-05-27 13:40 UTCepss_batch
2026-05-27 13:40 UTCepss_batch
2026-05-26 13:43 UTCepss_batch
2026-05-26 13:43 UTCepss_batch
2026-05-26 07:18 UTCepss_batch
2026-05-26 07:18 UTCepss_batch

Frequently asked(5)

What is CVE-2024-33531?

CVE-2024-33531 is a high vulnerability published on April 24, 2024. cdbattags lua-resty-jwt 0.2.3 allows attackers to bypass all JWT-parsing signature checks by crafting a JWT with an enc header with the value A256GCM.

When was CVE-2024-33531 disclosed?

CVE-2024-33531 was first published in the National Vulnerability Database on April 24, 2024, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2024-33531 actively exploited?

CVE-2024-33531 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 27.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2024-33531?

CVE-2024-33531 has a CVSS v3 base score of 8.1 (NVD).

How do I remediate CVE-2024-33531?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-33531, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-33531

Explore →

Is Your Infrastructure Affected by CVE-2024-33531?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2024-33531

📅 Published

🔄 Last Modified

🔗 References (6)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2024-33531?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (6)

Frequently asked(5)

Related CVEs(same CWE)