cve.bz

CVE-2026-13316 SSRF

4.4 mediumEPSS 0.1%

Medium (4.4). EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
A flaw has been found in foreman when HTTP parameters are modified in http_proxies_controller and http_proxy files. Attackers can perform an SSRF attack and steal cloud metadata service on AWS/GCP/Azure environment through foreman component.

Severity

CVSS 3.1

4.4 medium
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
EPSS
0.1% (unchanged from 0.1% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 4th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-06-30. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-918 Server-Side Request Forgery (SSRF)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-13316 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-13316?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-13316?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-13316 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-13316

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-13316](https://cve.bz/cve/badge/CVE-2026-13316.svg)](https://cve.bz/cve/CVE-2026-13316)

HTML:

<a href="https://cve.bz/cve/CVE-2026-13316"><img src="https://cve.bz/cve/badge/CVE-2026-13316.svg" alt="CVE-2026-13316"></a>

Affected

Versions

From the NVD's CPE matches.

ProductAffected
redhat:satellitefrom 6.0 through 6.19

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

Red Hat Product Security has assessed that this issue is not exploitable under the default configuration. Exploitation requires an attacker with sufficient privileges on the host where Foreman is installed to modify the relevant configuration files and to trigger the Server-Side Request Forgery (SSRF) condition.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

ProductPackageStateAdvisory
Red Hat Satellite 6foremanFix deferred
Red Hat Satellite 6satellite-utils:el8/foremanFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-13316.

Attack patterns (CAPEC)

  • CAPEC-664 Server Side Request Forgery Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON