Skip to content
statance
MenuClose
medium · CVSS 6.5

CVE-2026-74243

Quay: unauthenticated secscan notification endpoint in quay when psk is unset

Published 14 Aug 2026 · Source updated 1 Nov 2026 · Retrieved 2026-11-04 16:02 UTC · This record may be stale; verify the source

Monitor this CVE ↗Full CVE monitoring on Pro and Business

What happened?

A flaw was found in Red Hat Quay. When the SECURITY_SCANNER_V4_PSK (pre-shared key) is not set, a remote unauthenticated attacker can send POST requests to the security scanner notification endpoint. This allows the attacker to flood the notification queue and inject path traversal characters into Clair API URL paths. The primary consequence is worker resource exhaustion and blind path manipulation on the configured Clair host, potentially leading to a denial of service.

Description supplied by CVE Program. Formatting is simplified; follow the original advisory for full details.

Affected software and versions

Source-provided software and version information
SoftwareVersion informationFixed version
openshift-update-service/openshift-update-service-rhel8Red HatDefault status: affectedSee vendor advisory
quay/quay-rhel8Red HatDefault status: affectedSee vendor advisory
quay/quay-rhel9Red HatDefault status: affectedSee 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.

CISA data retrieved 2026-11-06 16:38 UTC. Check CISA ↗

How to respond

  1. Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
  2. 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.
  3. Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.

Sources and remediation references

This public advisory does not determine whether a particular server is affected. Records are refreshed as sources change; verify urgent decisions against the original advisory.

← Browse the public CVE feed