Bug 2516144 (CVE-2026-74247)

Summary: CVE-2026-74247 quay: SSRF via build archive_url in Quay build API
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security <prodsec-ir-bot>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: aruklets, doconnor
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A flaw was found in Red Hat Quay. A user with FEATURE_BUILD_SUPPORT enabled and repository write access can exploit a Server-Side Request Forgery (SSRF) vulnerability within the build API. This allows the user to provide a malicious URL, causing the Quay builder to make requests to internal network addresses. Such an action could lead to the disclosure of sensitive internal information.
 Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2026-08-14 19:51:40 UTC 
A flaw was found in Red Hat Quay's build API. The endpoints/api/build.py endpoint accepts an archive_url parameter with only an http/https scheme check and no SSRF validation. The URL is stored and passed to the builder fetch path, allowing a user with FEATURE_BUILD_SUPPORT enabled and repository write access to make the Quay builder issue requests to internal network addresses. This is a distinct code path from CVE-2026-16910 (webhook/Slack notification SSRF) with different privilege requirements and impact profile.