Quick answers
- Is CVE-2026-74244 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-74244 being exploited in the wild.
- How severe is CVE-2026-74244?
- Medium severity, with a CVSS score of 5.9, published 14 August 2026.
- Which products and versions are affected?
- Red Hat Quay <UNKNOWN>.
- Is there a fix for CVE-2026-74244?
- 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-74244 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-74244?
- Check whether you run Redhat Quay. 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 an improper cryptographic signature verification (CWE-347) in Red Hat Quay's Stripe billing webhook handler at the `/webhooks/stripe` endpoint. The handler accepts forged billing event requests in JSON format without validating the Stripe-Signature header, allowing unauthenticated attackers to send crafted requests. An attacker with network access to the endpoint can trigger unauthorized build quota resets and generate spurious billing notifications to administrators. The vulnerability exists even when the billing feature is disabled, though impact is reduced in self-hosted deployments using FakeStripe. Network-level mitigation is available by restricting access to the endpoint from untrusted sources.
Affected products
- Red Hat Quay <UNKNOWN>
Timeline
- 2026-08-14: disclosed