{}

{}

{}

{"acknowledgement": "Red Hat would like to thank meifukun (https://github.com/meifukun) for reporting this issue.", "bugzilla": {"description": "quay: Local file inclusion via file:// scheme in Quay custom build trigger", "id": "2516146", "url": "https://bugzilla.redhat.com/show_bug.cgi?id=2516146"}, "csaw": false, "cvss3": {"cvss3_base_score": "7.7", "cvss3_scoring_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N", "status": "draft"}, "cwe": "CWE-918", "details": ["A flaw was found in Red Hat Quay's custom build trigger handler. This vulnerability allows a user with organization repository administrative privileges and the FEATURE_BUILD_SUPPORT enabled to read arbitrary files on the build worker. This is possible due to insufficient validation of the build source configuration, which permits the use of a file:// Uniform Resource Identifier (URI) scheme. Exploiting this flaw can lead to unauthorized information disclosure."], "mitigation": {"lang": "en:us", "value": "To reduce exposure, disable the FEATURE_BUILD_SUPPORT feature in Red Hat Quay if it is not actively used. If this feature is required, restrict organization repository admin privileges to trusted personnel only."}, "name": "CVE-2026-74246", "package_state": [{"cpe": "cpe:/a:redhat:openshift_update_service:5", "fix_state": "Not affected", "package_name": "openshift-update-service/openshift-update-service-rhel8", "product_name": "Red Hat OpenShift Update Service"}, {"cpe": "cpe:/a:redhat:quay:3", "fix_state": "Not affected", "package_name": "quay/quay-rhel8", "product_name": "Red Hat Quay 3"}, {"cpe": "cpe:/a:redhat:quay:3", "fix_state": "Not affected", "package_name": "quay/quay-rhel9", "product_name": "Red Hat Quay 3"}], "public_date": "2026-09-28T00:00:00Z", "references": ["https://www.cve.org/CVERecord?id=CVE-2026-74246\nhttps://nvd.nist.gov/vuln/detail/CVE-2026-74246"], "statement": "This flaw in Red Hat Quay is rated Important. A user with organization repository admin privileges and the `FEATURE_BUILD_SUPPORT` enabled can exploit a lack of scheme validation in the custom build trigger handler. This allows for local file inclusion via the `file://` URI scheme, leading to the disclosure of arbitrary files accessible to the build worker process.", "threat_severity": "Important"}

{}