CVE-2026-74244: CWE-347
Source GCVE Database
Not known to be exploited · CVSS 5.9 Medium.
Data as of 13 Nov 2026, 23:54 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 14 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Red HatRed Hat OpenShift Update Service | Affected– | Fixed in– |
| Red HatRed Hat Quay 3 | Affected– | Fixed in– |
AI-suggested
Red Hat advises restricting network access to the /webhooks/stripe endpoint by configuring firewalls to allow connections only from trusted Stripe IP addresses. If Stripe billing integration is not used, blocking access to this endpoint entirely is recommended. These network restrictions prevent unauthenticated attackers from forging billing events. Ensure that any network configuration changes are applied and services restarted as necessary.
Description
A vulnerability in Red Hat Quay's Stripe billing webhook handler allows unauthenticated attackers to forge billing events by sending crafted JSON requests to the /webhooks/stripe endpoint without validating the Stripe-Signature header. Exploitation can reset a namespace's build quota to its maximum and cause unsolicited billing emails to be sent to namespace administrators. The flaw exists even if the billing feature is disabled, though impact is reduced in self-hosted deployments using FakeStripe. No official patch is currently available; mitigation involves restricting network access to the webhook endpoint to trusted Stripe IPs or blocking it if unused.