# CVE-2026-84185: Jwcrypto: jwcrypto: general json jws kid binding bypass during jwkset verification

> Attackers can bypass authorization checks in applications using jwcrypto by exploiting a key ID binding flaw during JWS verification.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Sep 2026
- **Updated:** 4 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-84185, UBUNTU-CVE-2026-84185

## What is CVE-2026-84185?

CVE-2026-84185 is a medium-severity authentication bypass vulnerability in Red Hat Ansible Automation Platform 2, published on 3 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw was found in the jwcrypto library, which is used for implementing Javascript Object Signing and Encryption (JOSE) standards. The issue occurs when the library verifies a General JSON Serialization JWS using a set of keys. Due to a coding error, the library fails to correctly identify the specific key ID (kid) and may instead accept a signature made by any valid key in the set. This can allow an attacker with a valid key to bypass authorization checks in applications that rely on the key ID to identify specific tenants or users.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

## Which versions are affected by CVE-2026-84185?


## How do I fix CVE-2026-84185?

Apply the vendor's patch.

## Is CVE-2026-84185 being exploited?

There is no known exploitation of CVE-2026-84185 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-84185 and fix it if it is affected.

What it is: CVE-2026-84185 is a medium-severity authentication bypass vulnerability in Red Hat Ansible Automation Platform 2, published on 3 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-84185 in the wild and no public exploit code.

Affected product: Red Hat Ansible Automation Platform 2. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-84185/ (Markdown: https://insights.sbomify.com/CVE-2026-84185/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-84185
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-84185
- OSV: https://osv.dev/vulnerability/CVE-2026-84185

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-84185/
Summaries are generated and may contain mistakes; the official description above is the record.