Is CVE-2026-84185 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-84185 being exploited in the wild.

How severe is CVE-2026-84185?

Medium severity, with a CVSS score of 5.9, published 3 September 2026.

Is there a fix for CVE-2026-84185?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-84185 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-84185?

Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-84185: python-jwcrypto key ID binding bypass in JWS verification

CVE-2026-84185 · Severity: medium · CVSS 5.9 · Published 2026-09-03

The jwcrypto library, which handles cryptographic signing and encryption for web applications, contains a flaw in how it validates signed messages when multiple keys are in use. Due to a coding error, the library may accept a signature from any valid key instead of requiring the specific key identified in the message. An attacker with access to any legitimate signing key could forge or manipulate messages to impersonate other users or tenants, bypassing identity checks that applications rely on.

Quick answers

Is CVE-2026-84185 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-84185 being exploited in the wild.
How severe is CVE-2026-84185?: Medium severity, with a CVSS score of 5.9, published 3 September 2026.
Which products and versions are affected?: jwcrypto jwcrypto.
Is there a fix for CVE-2026-84185?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-84185 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-84185?: Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is a cryptographic signature verification bypass (CWE-347) in the jwcrypto library's handling of General JSON Serialization JWS (JSON Web Signature). When verifying a JWS against a set of keys (JWKSet), the library fails to correctly identify and enforce the key ID (kid) parameter due to an incorrect type check in the verification logic. An attacker who possesses a valid signing key trusted by the application can exploit this to bypass key binding constraints, potentially impersonating other identities or tenants. The attack requires the attacker to already hold a valid signing key within the trusted key set. A fix is expected from the jwcrypto maintainers; check the upstream project repository for patched versions.

Affected products

jwcrypto jwcrypto

Timeline

2026-09-03: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.