Quick answers
- Is CVE-2026-6912 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-6912 being exploited in the wild.
- How severe is CVE-2026-6912?
- Critical severity, with a CVSS score of 9.8, published 24 April 2026.
- Which products and versions are affected?
- Amazon Web Services Ops Wheel v2 deployments PR-163 and earlier.
- Is there a fix for CVE-2026-6912?
- A patch was published on 2026-04-24. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-6912 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-6912?
- Check whether you run Amazon AWS or Amazon Web Services Ops Wheel at an affected version. 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
AWS Ops Wheel v2 is affected by two distinct vulnerabilities. CVE-2026-6911 is an authentication bypass caused by the failure to enforce JWT token signature verification in the v2 API; an unauthenticated remote attacker can craft a malicious token to gain full administrative access to the API Gateway endpoint. CVE-2026-6912 is a privilege escalation vulnerability where insufficient restrictions on Cognito User Pool attribute write permissions allow an authenticated user to modify their own attributes to gain elevated privileges. These issues have been addressed in PR #164 and PR #165, respectively.
Affected products
- AWS Ops Wheel v2 deployments PR-163 and earlier
Identifiers
- CVE-2026-6912
- CVE-2026-6911
Timeline
- 2026-04-24: disclosed
- 2026-04-24: patched
- 2026-04-24: advisory