{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2026-74247 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-74247 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-74247 is a medium-severity server-side request forgery vulnerability in Red Hat OpenShift Update Service, published on 14 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-74247 and fix it if it is affected.\n\nWhat it is: CVE-2026-74247 is a medium-severity server-side request forgery vulnerability in Red Hat OpenShift Update Service, published on 14 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-74247 in the wild and no public exploit code.\n\nAffected product: Red Hat OpenShift Update Service. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-74247/ (Markdown: https://insights.sbomify.com/CVE-2026-74247/index.md)","id":"CVE-2026-74247","markdown":"https://insights.sbomify.com/CVE-2026-74247/index.md","name":"CVE-2026-74247","record":{"aliases":["GHSA-rg7f-fcx2-cjw3"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Red Hat Quay","requires_auth":"low_privilege","summary":"A user with repository write access can exploit SSRF in the build API to access internal network resources and disclose sensitive information.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"openshift_update_service","vendor":"redhat"},{"product":"quay","vendor":"redhat"}],"cvss":{"score":4.2,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Quay: ssrf via build archive_url in quay build api","id":"CVE-2026-74247","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Missing authorization in Octavia","id":"CVE-2026-74248"},"packages":[],"prev":{"headline":"Quay: unauthenticated exported logs download in quay","id":"CVE-2026-74245"},"products":["Red Hat OpenShift Update Service","Red Hat Quay 3"],"published":"2026-08-14","related":[{"cvss_score":6.5,"headline":"Quay: unauthenticated secscan notification endpoint in quay when psk is unset","id":"CVE-2026-74243","kev_date_added":null,"published":"2026-08-14"},{"cvss_score":6.4,"headline":"Osus-operator: privilege escalation via excessive /etc/passwd permissions","id":"CVE-2025-57854","kev_date_added":null,"published":"2026-04-08"},{"cvss_score":5.9,"headline":"Quay: stripe webhook accepts forged events without signature verification in quay","id":"CVE-2026-74244","kev_date_added":null,"published":"2026-08-14"},{"cvss_score":5.9,"headline":"Quay: unauthenticated exported logs download in quay","id":"CVE-2026-74245","kev_date_added":null,"published":"2026-08-14"},{"cvss_score":5.4,"headline":"Quay: jwt claim validation bypasses in quay federated robot and sso authentication","id":"CVE-2026-74240","kev_date_added":null,"published":"2026-08-14"},{"cvss_score":5.3,"headline":"Quay: repository notification uuid idor in quay api","id":"CVE-2026-74242","kev_date_added":null,"published":"2026-08-14"},{"cvss_score":4.8,"headline":"Quay: ldap referral filter injection in quay external ldap authentication","id":"CVE-2026-74241","kev_date_added":null,"published":"2026-08-14"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-17","vendors":["Red Hat"]},"summary":"A user with repository write access can exploit SSRF in the build API to access internal network resources and disclose sensitive information.","url":"https://insights.sbomify.com/CVE-2026-74247/"}