CVE-2026-84185
Jwcrypto: jwcrypto: general json jws kid binding bypass during jwkset verification
What happened?
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.
Affected software and versions
| Software | Version information | Fixed version |
|---|---|---|
| ansible-automation-platform-24/controller-rhel8Red Hat | Default status: affected | See vendor advisory |
| ansible-automation-platform-24/lightspeed-rhel8Red Hat | Default status: affected | See vendor advisory |
| ansible-automation-platform-25/controller-rhel8Red Hat | Default status: affected | See vendor advisory |
| ansible-automation-platform-25/gateway-rhel8Red Hat | Default status: affected | See vendor advisory |
| ansible-automation-platform-25/lightspeed-rhel8Red Hat | Default status: affected | See vendor advisory |
| ansible-automation-platform-26/controller-rhel9Red Hat | Default status: affected | See vendor advisory |
| ansible-automation-platform-26/gateway-rhel9Red Hat | Default status: affected | See vendor advisory |
| ansible-automation-platform-26/lightspeed-rhel9Red Hat | Default status: affected | See vendor advisory |
| ansible-automation-platform-27/gateway-rhel9Red Hat | Default status: affected | See vendor advisory |
| ansible-automation-platform-27/lightspeed-rhel9Red Hat | Default status: affected | See vendor advisory |
| automation-controllerRed Hat | Default status: affected | See vendor advisory |
| python3.11-jwcryptoRed Hat | Default status: affected | See vendor advisory |
| python3.12-jwcryptoRed Hat | Default status: affected | See vendor advisory |
| python-jwcryptoRed Hat | Default status: affected | See vendor advisory |
| python-jwcryptoRed Hat | Default status: affected | See vendor advisory |
| idm:client/python-jwcryptoRed Hat | Default status: affected | See vendor advisory |
| idm:DL1/python-jwcryptoRed Hat | Default status: affected | See vendor advisory |
| python-jwcryptoRed Hat | Default status: affected | See vendor advisory |
| rhoai/odh-feature-server-rhel9Red Hat | Default status: unaffected | See vendor advisory |
| rhoai/odh-kserve-storage-initializer-rhel9Red Hat | Default status: unaffected | See vendor advisory |
| rhosp-rhel8/openstack-mistral-executorRed Hat | Default status: unaffected | See vendor advisory |
| rhosp-rhel8/openstack-nova-apiRed Hat | Default status: unaffected | See vendor advisory |
| rhosp-rhel8/openstack-nova-compute-ironicRed Hat | Default status: unaffected | See vendor advisory |
| rhosp-rhel8/openstack-novajoin-baseRed Hat | Default status: unaffected | See vendor advisory |
| rhosp-rhel8/openstack-novajoin-notifierRed Hat | Default status: unaffected | See vendor advisory |
| rhosp-rhel8/openstack-novajoin-serverRed Hat | Default status: unaffected | See vendor advisory |
| rhosp-rhel8/openstack-tempestRed Hat | Default status: unaffected | See vendor advisory |
| rhosp-rhel8/openstack-tripleoclientRed Hat | Default status: unaffected | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.