VulnerabilityPublished 14 Aug 2026Updated 1 Nov 2026

CVE-2026-74247: Red Hat OpenShift Update Service · Server-Side Request Forgery

Affects Red Hat OpenShift Update ServiceSource CVE Database V5

Compare

Not known to be exploited · CVSS 4.2 Medium.

Data as of 12 Nov 2026, 23:24 UTC

CVSS 3.1 base score

4.2Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (redhat)	CVSS 3.1	4.2

EPSS: 0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: High
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 14 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Red Hat OpenShift Update Serviceopenshift-update-service/openshift-update-service-rhel8	Affected–	Fixed in–
Red Hat Quay 3quay/quay-rhel8	Affected–	Fixed in–
Red Hat Quay 3quay/quay-rhel9	Affected–	Fixed in–

AI-suggested

Red Hat advises disabling the FEATURE_BUILD_SUPPORT feature in Red Hat Quay if it is not essential. This prevents access to the vulnerable build API endpoint and mitigates the SSRF vulnerability. Users should refer to Red Hat Quay product documentation for instructions on managing and disabling features.

Description

CVE-2026-74247 is a Server-Side Request Forgery (SSRF) vulnerability in Red Hat Quay's build API. It affects users with FEATURE_BUILD_SUPPORT enabled and repository write access, allowing them to supply malicious URLs that cause the Quay builder to make requests to internal network addresses. This could lead to disclosure of sensitive internal information. The vulnerability requires specific configuration and privileges, limiting its attack surface. The vendor recommends disabling the FEATURE_BUILD_SUPPORT feature if it is not essential to mitigate the risk.

Impact

Successful exploitation allows an authenticated user with repository write access and FEATURE_BUILD_SUPPORT enabled to perform SSRF attacks via the build API, potentially disclosing sensitive internal network information. The attack surface is limited by the need for specific configuration and privileges. The impact is rated as medium with low confidentiality and integrity impacts and no availability impact.

Summary

This vulnerability exists in Red Hat Quay's build API where an authenticated user with repository write access and the FEATURE_BUILD_SUPPORT feature enabled can exploit an SSRF flaw. By providing a crafted URL, the user can cause the Quay builder to send requests to internal network resources, potentially exposing sensitive information. Exploitation requires the FEATURE_BUILD_SUPPORT feature to be enabled and appropriate repository permissions. Red Hat classifies this as a moderate impact issue with a CVSS 3.1 base score of 4.2, reflecting low confidentiality and integrity impacts and no availability impact. The vendor advisory explicitly recommends disabling FEATURE_BUILD_SUPPORT if not needed to prevent exploitation.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 1 Nov 2026, 11:19 UTC

Technical details

References

Community reviews

Related threats