jose vulnerable to resource exhaustion via specifically crafted JWE with compressed plaintext
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
cve-program · CVE-2024-28176
Publishedjose is JavaScript module for JSON Object Signing and Encryption, providing support for JSON Web Tokens (JWT), JSON Web Signature (JWS), JSON Web Encryption (JWE), JSON Web Key (JWK), JSON Web Key Set (JWKS), and more. A vulnerability has been identified in the JSON Web Encryption (JWE) decryption interfaces, specifically related to the support for decompressing plaintext after its decryption. Under certain conditions it is possible to have the user's environment consume unreasonable amount of CPU time or memory during JWE Decryption operations. This issue has been patched in versions 2.0.7 and 4.15.5.
- Source published
- 9 Mar 2024 00:43:06 UTC
- Source modified
- 13 Feb 2025 17:47:26 UTC
- Saved here
- 23 Oct 2026 15:48:27 UTC
- Source terms
- CVE Program Terms of Use
Original source record · Cite this exact observation · Complete original publisher JSON
Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 3.1 · 4.9 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
euvd · EUVD-2024-0938
Publishedjose is JavaScript module for JSON Object Signing and Encryption, providing support for JSON Web Tokens (JWT), JSON Web Signature (JWS), JSON Web Encryption (JWE), JSON Web Key (JWK), JSON Web Key Set (JWKS), and more. A vulnerability has been identified in the JSON Web Encryption (JWE) decryption interfaces, specifically related to the support for decompressing plaintext after its decryption. Under certain conditions it is possible to have the user's environment consume unreasonable amount of CPU time or memory during JWE Decryption operations. This issue has been patched in versions 2.0.7 and 4.15.5.
Additional publisher context
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
Original publisher date fields
datePublished: Mar 9, 2024, 12:43:06 AM
dateUpdated: Feb 13, 2025, 5:47:26 PM
19 related source bulletins · separate from aliases
RHSA-2024:0041: Red Hat Security Advisory: OpenShift Container Platform 4.16.0 bug fix and security update
CVE-2019-25210 · CVE-2023-45142 · CVE-2023-45289 · CVE-2023-47108 · CVE-2023-48795 · CVE-2023-49569 · CVE-2024-0874 · CVE-2024-22189 · CVE-2024-24783 · CVE-2024-24784 · CVE-2024-24785 · CVE-2024-24786 · CVE-2024-28110 · CVE-2024-28176 · CVE-2024-28180 · CVE-2024-28849 · CVE-2024-29180
RHBA-2024:1775: Red Hat Bug Fix Advisory: Multicluster Engine for Kubernetes 2.5.2 bug fixes and container updates
CVE-2024-21501 · CVE-2024-28176
RHBA-2025:1772: Red Hat Bug Fix Advisory: Updated 7.1 container image is now available in the Red Hat Ecosystem Catalog
CVE-2023-45287 · CVE-2023-45288 · CVE-2024-24786 · CVE-2024-28176 · CVE-2024-28180 · CVE-2024-30255 · CVE-2024-34155 · CVE-2024-34156 · CVE-2024-41184
WID-SEC-W-2024-1474: Red Hat OpenShift Container Platform: Mehrere Schwachstellen
CVE-2019-25210 · CVE-2023-29483 · CVE-2023-45142 · CVE-2023-45289 · CVE-2023-45290 · CVE-2023-47108 · CVE-2023-48795 · CVE-2023-52425 · CVE-2024-0874 · CVE-2024-1394 · CVE-2024-22189 · CVE-2024-2398 · CVE-2024-24783 · CVE-2024-24784 · CVE-2024-24785 · CVE-2024-24786 · CVE-2024-28110 · CVE-2024-28176 · CVE-2024-28180 · CVE-2024-28757 · CVE-2024-28849 · CVE-2024-29180 · CVE-2024-3177 · CVE-2024-3727
RHBA-2024:3555: Red Hat Bug Fix Advisory: multicluster engine for Kubernetes 2.4.5 bug fixes and container updates
CVE-2023-26159 · CVE-2024-4068 · CVE-2024-21501 · CVE-2024-28176
RHBA-2024:3593: Red Hat Bug Fix Advisory: Red Hat Advanced Cluster Management 2.9.4 bug fixes and container updates
CVE-2023-26159 · CVE-2024-4068 · CVE-2024-21501 · CVE-2024-28176
RHSA-2024:5294: Red Hat Security Advisory: jose security update
CVE-2023-50967 · CVE-2024-28176
WID-SEC-W-2024-0767: IBM App Connect Enterprise: Mehrere Schwachstellen
CVE-2024-27307 · CVE-2024-28176
RHSA-2024:0045: Red Hat Security Advisory: OpenShift Container Platform 4.16.0 security update
CVE-2023-29483 · CVE-2023-45289 · CVE-2023-45290 · CVE-2024-3727 · CVE-2024-24783 · CVE-2024-24784 · CVE-2024-24785 · CVE-2024-24786 · CVE-2024-28176
RHSA-2024:3968: Red Hat Security Advisory: container-tools:rhel8 bug fix and enhancement update
CVE-2024-28176 · CVE-2024-28180
RHSA-2024:8676: Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.17.0 Security, Enhancement, & Bug Fix Update
CVE-2023-26136 · CVE-2023-26364 · CVE-2024-24786 · CVE-2024-24789 · CVE-2024-28176 · CVE-2024-41818 · CVE-2024-43788 · CVE-2024-43796 · CVE-2024-43799 · CVE-2024-43800 · CVE-2024-45296 · CVE-2024-45590
RHSA-2024:3826: Red Hat Security Advisory: podman security and bug fix update
CVE-2023-45290 · CVE-2024-28176 · CVE-2024-28180
RHSA-2024:6755: Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.16.2 security and bug fix update
CVE-2023-39325 · CVE-2024-6104 · CVE-2024-24789 · CVE-2024-28176 · CVE-2024-28863 · CVE-2024-29180 · CVE-2024-37890 · CVE-2024-41818
RHSA-2024:3827: Red Hat Security Advisory: buildah security and bug fix update
CVE-2023-45290 · CVE-2024-28176 · CVE-2024-28180
RHBA-2024:1793: Red Hat Bug Fix Advisory: Red Hat Advanced Cluster Management 2.10.1 bug fix advisory
CVE-2024-21501 · CVE-2024-28176
RHBA-2025:1479: Red Hat Bug Fix Advisory: Updated 5.3 container image is now available in the Red Hat Ecosystem Catalog.
CVE-2023-4822 · CVE-2023-6152 · CVE-2023-39326 · CVE-2023-45288 · CVE-2024-1313 · CVE-2024-1442 · CVE-2024-28176 · CVE-2024-28180 · CVE-2024-30255 · CVE-2024-34155 · CVE-2024-34156
RHSA-2024:4591: Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.16.0 security, enhancement & bug fix update
CVE-2023-43646 · CVE-2023-47108 · CVE-2024-1394 · CVE-2024-5042 · CVE-2024-24783 · CVE-2024-24785 · CVE-2024-24786 · CVE-2024-28176 · CVE-2024-28180 · CVE-2024-28863 · CVE-2024-37890
RHSA-2024:9181: Red Hat Security Advisory: jose security update
CVE-2023-50967 · CVE-2024-28176
RHSA-2024:5094: Red Hat Security Advisory: Red Hat OpenShift Service Mesh Containers for 2.6.0 security update
CVE-2018-12608 · CVE-2024-22189 · CVE-2024-24789 · CVE-2024-28176
- Source published
- Mar 9, 2024, 12:43:06 AM (timezone not stated)
- Source modified
- Feb 13, 2025, 5:47:26 PM (timezone not stated)
- Saved here
- 15 Nov 2026 01:52:36 UTC
- Source terms
- ENISA EUVD · source terms and attribution apply
Original source record · Cite this exact observation · Complete original publisher JSON
Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
EUVD CVSS 3.1 · 4.9 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
nvd · CVE-2024-28176
Publishedjose is JavaScript module for JSON Object Signing and Encryption, providing support for JSON Web Tokens (JWT), JSON Web Signature (JWS), JSON Web Encryption (JWE), JSON Web Key (JWK), JSON Web Key Set (JWKS), and more. A vulnerability has been identified in the JSON Web Encryption (JWE) decryption interfaces, specifically related to the support for decompressing plaintext after its decryption. Under certain conditions it is possible to have the user's environment consume unreasonable amount of CPU time or memory during JWE Decryption operations. This issue has been patched in versions 2.0.7 and 4.15.5.
Additional publisher context
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Analyzed
Weakness classifications: CWE-400
Original publisher date fields
published: 2024-03-09T01:15:07.147
lastModified: 2026-06-17T07:21:08.920
2 source CPE criteria · context only
- cpe:2.3:a:jose_project:jose:*:*:*:*:*:node.js:*:*
- cpe:2.3:o:fedoraproject:fedora:*:*:*:*:*:*:*:*
The original JSON retains the logical configuration operators, exclusions and version bounds.
- Source published
- 9 Mar 2024 01:15:07 UTC
- Source modified
- 17 Jun 2026 07:21:08 UTC
- Saved here
- 24 Oct 2026 23:17:28 UTC
- Source terms
- NIST NVD usage terms; underlying source attribution retained
Original source record · Cite this exact observation · Complete original publisher JSON
Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 3.1 · [email protected] · Secondary · 4.9 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
CVSS 3.1 · [email protected] · Primary · 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
osv · GHSA-hhhv-q57g-882q
PublishedA vulnerability has been identified in the JSON Web Encryption (JWE) decryption interfaces, specifically related to the [support for decompressing plaintext after its decryption](https://www.rfc-editor.org/rfc/rfc7516.html#section-4.1.3). This allows an adversary to exploit specific scenarios where the compression ratio becomes exceptionally high. As a result, the length of the JWE token, which is determined by the compressed content's size, can land below application-defined limits. In such cases, other existing application level mechanisms for preventing resource exhaustion may be rendered ineffective. Note that as per [RFC 8725](https://www.rfc-editor.org/rfc/rfc8725.html#name-avoid-compression-of-encryp) compression of data SHOULD NOT be done before encryption, because such compressed data often reveals information about the plaintext. For this reason the v5.x major version of `jose` removed support for compressed payloads entirely and is therefore NOT affected by this advisory. ### Impact Under certain conditions it is possible to have the user's environment consume unreasonable amount of CPU time or memory during JWE Decryption operations. ### Affected users The impact is limited only to Node.js users utilizing the JWE decryption APIs to decrypt JWEs from untrusted sources. You are NOT affected if any of the following applies to you - Your code uses jose version v5.x where JWE Compression is not supported anymore - Your code runs in an environment other than Node.js (e.g. Deno, CF Workers), which is the only runtime where JWE Compression is implemented out of the box - Your code does not use the JWE decryption APIs - Your code only accepts JWEs produced by trusted sources ### Patches `v2.0.7` and `v4.15.5` releases limit the decompression routine to only allow decompressing up to 250 kB of plaintext. In v4.x it is possible to further adjust this limit via the `inflateRaw` decryption option implementation. In v2.x it is possible to further adjust this limit via the `inflateRawSyncLimit` decryption option. ### Workarounds If you cannot upgrade and do not want to support compressed JWEs you may detect and reject these tokens early by checking the token's protected header ```js const { zip } = jose.decodeProtectedHeader(token) if (zip !== undefined) { throw new Error('JWE Compression is not supported') } ``` If you wish to continue supporting JWEs with compressed payloads in these legacy release lines you must upgrade (v1.x and v2.x to version v2.0.7, v3.x and v4.x to version v4.15.5) and review the limits put forth by the patched releases. ### For more information If you have any questions or comments about this advisory please open a discussion in the project's [repository](https://github.com/panva/jose/discussions/new?category=q-a&title=GHSA-hhhv-q57g-882q%20advisory%20question)
- Source published
- 7 Mar 2024 17:40:57 UTC
- Source modified
- 10 Sep 2026 03:50:10 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- GitHub Advisory Database · CC-BY-4.0
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS_V3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Publisher rating · MODERATE