Quick answers
- Is CVE-2026-74243 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-74243 being exploited in the wild.
- How severe is CVE-2026-74243?
- Medium severity, with a CVSS score of 6.5, published 14 August 2026.
- Which products and versions are affected?
- Red Hat Quay.
- Is there a fix for CVE-2026-74243?
- 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-74243 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-74243?
- 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
This vulnerability is a missing authentication issue (CWE-306) in the security scanner notification endpoint when SECURITY_SCANNER_V4_PSK is not set. A remote unauthenticated attacker can send POST requests to the endpoint over the network with no privileges required, allowing them to flood the notification queue and inject path traversal characters into Clair API URLs. The attack causes worker resource exhaustion and blind path manipulation on the Clair host, potentially resulting in denial of service. The vulnerability primarily affects standalone Quay installations; operator-managed deployments automatically generate the pre-shared key. Mitigation involves configuring the SECURITY_SCANNER_V4_PSK parameter and restarting the service.
Affected products
- Red Hat Quay
Timeline
- 2026-08-14: disclosed