CVE-2026-13316

MEDIUMPre-NVD 4.44.4—
EchelonGraph scoreHIGH confidence

Score 4.4 from GitHub Security Advisory published 2026-06-30. a secondary CVSS source baseline 4.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
4.4
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.4Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
4.4
EG Score
4.4(high)
EG Risk
20(Track)
EG Risk 20/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity44% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
1.2%
KEV
Not listed

Published

June 30, 2026

Last Modified

July 6, 2026

Advisory Details (2)

Auto-updated Jun 30, 2026
Patch available. Sources: redhat.
redhat

2490345 – (CVE-2026-13316) CVE-2026-13316 Foreman: SSRF to cloud metada service through unvalidated test_url parameters in Foreman config

https://bugzilla.redhat.com/show_bug.cgi?id=2490345
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-13316

Vendor Advisories for CVE-2026-13316(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 40× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-24 14:17 UTCEPSS rescore
  2. 2026-07-23 03:05 UTCEG score recompute
  3. 2026-07-21 15:24 UTCEPSS rescore
  4. 2026-07-20 17:08 UTCEPSS rescore
  5. 2026-07-19 14:30 UTCEPSS rescore
  6. 2026-07-18 10:04 UTCEPSS rescore
  7. 2026-07-17 05:26 UTCGHSA enrichment
  8. 2026-07-16 17:02 UTCEPSS rescore
  9. 2026-07-16 05:53 UTCGHSA enrichment
  10. 2026-07-15 16:57 UTCEPSS rescore
  11. 2026-07-15 06:20 UTCGHSA enrichment
  12. 2026-07-14 06:47 UTCGHSA enrichment
  13. 2026-07-13 22:30 UTCEPSS rescore
  14. 2026-07-13 07:05 UTCGHSA enrichment
  15. 2026-07-13 06:12 UTCEPSS rescore
  16. 2026-07-12 07:28 UTCGHSA enrichment
  17. 2026-07-12 05:46 UTCEPSS rescore
  18. 2026-07-11 08:27 UTCEPSS rescore
  19. 2026-07-11 07:54 UTCGHSA enrichment
  20. 2026-07-10 08:20 UTCGHSA enrichment
  21. 2026-07-09 19:10 UTCEPSS rescore
  22. 2026-07-09 08:47 UTCGHSA enrichment
  23. 2026-07-08 09:13 UTCGHSA enrichment
  24. 2026-07-07 13:46 UTCEPSS rescore
  25. 2026-07-07 09:40 UTCGHSA enrichment
Show 15 more
  1. 2026-07-06 10:07 UTCGHSA enrichment
  2. 2026-07-06 02:23 UTCEPSS rescore
  3. 2026-07-05 10:31 UTCGHSA enrichment
  4. 2026-07-05 02:30 UTCEPSS rescore
  5. 2026-07-05 02:30 UTCEPSS rescore
  6. 2026-07-04 10:57 UTCGHSA enrichment
  7. 2026-07-04 06:31 UTCEPSS rescore
  8. 2026-07-03 11:23 UTCGHSA enrichment
  9. 2026-07-02 11:41 UTCGHSA enrichment
  10. 2026-07-01 15:06 UTCEPSS rescore
  11. 2026-07-01 15:06 UTCEPSS rescore
  12. 2026-07-01 12:06 UTCGHSA enrichment
  13. 2026-06-30 12:33 UTCEG score recompute
  14. 2026-06-30 12:33 UTCGHSA enrichment
  15. 2026-06-30 12:32 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-13316?
CVE-2026-13316 is a medium vulnerability published on June 30, 2026. A flaw has been found in foreman when HTTP parameters are modified in httpproxiescontroller and http_proxy files. Attackers can perform an SSRF attack and steal cloud metadata service on AWS/GCP/Azure environment through foreman component.
When was CVE-2026-13316 disclosed?
CVE-2026-13316 was first published in the National Vulnerability Database on June 30, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-13316 actively exploited?
CVE-2026-13316 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-13316?
CVE-2026-13316 has a CVSS v3 base score of 4.4 (NVD).
How do I remediate CVE-2026-13316?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-13316, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-13316

Explore →

Is Your Infrastructure Affected by CVE-2026-13316?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs