# CVE-2026-74243: Quay: unauthenticated secscan notification endpoint in quay when psk is unset

> Unauthenticated attackers can cause denial of service and path manipulation in Red Hat Quay if the security scanner pre-shared key is not configured.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Aug 2026
- **Updated:** 18 Aug 2026
- **Also known as:** GHSA-vxqv-j38r-6jmm

## What is CVE-2026-74243?

CVE-2026-74243 is a medium-severity missing authorization vulnerability in Red Hat OpenShift Update Service, published on 14 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-74243?

It affects 2 products.


Products: Redhat Openshift Update Service, Redhat Quay.

## How do I fix CVE-2026-74243?

No fix has been published for CVE-2026-74243 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-74243 being exploited?

There is no known exploitation of CVE-2026-74243 in the wild and no public exploit code.

## Other vulnerabilities in Red Hat OpenShift Update Service

- [CVE-2025-57854](https://insights.sbomify.com/CVE-2025-57854/): Osus-operator: privilege escalation via excessive /etc/passwd permissions (medium 6.4)
- [CVE-2026-74244](https://insights.sbomify.com/CVE-2026-74244/): Quay: stripe webhook accepts forged events without signature verification in quay (medium 5.9)
- [CVE-2026-74245](https://insights.sbomify.com/CVE-2026-74245/): Quay: unauthenticated exported logs download in quay (medium 5.9)
- [CVE-2026-74240](https://insights.sbomify.com/CVE-2026-74240/): Quay: jwt claim validation bypasses in quay federated robot and sso authentication (medium 5.4)
- [CVE-2026-74242](https://insights.sbomify.com/CVE-2026-74242/): Quay: repository notification uuid idor in quay api (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-74243 and fix it if it is affected.

What it is: CVE-2026-74243 is a medium-severity missing authorization vulnerability in Red Hat OpenShift Update Service, published on 14 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-74243 in the wild and no public exploit code.

Affected product: Red Hat OpenShift Update Service. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-74243/ (Markdown: https://insights.sbomify.com/CVE-2026-74243/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-74243
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-74243
- OSV: https://osv.dev/vulnerability/CVE-2026-74243

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-74243/
Summaries are generated and may contain mistakes; the official description above is the record.