CVE-2026-71493

MEDIUMPre-NVD 5.95.9
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 5.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (44th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
5.9EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 5.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Infracost provides cloud cost intelligence for engineers, AI coding agents, and CI/CD. Prior to 0.10.45, the readFile, pathExists, isDir, and matchPaths template functions in internal/config/template/parser.go use a lexical filepath.Rel check and a leaf-only os.Lstat check that do not resolve an intermediate directory symlink. A repository can contain a path such as evil/file where evil points outside the checkout, causing os.ReadFile and related operations to follow the symlink and read runner-accessible files. The resulting content is rendered into generated configuration and can be surfaced through the Infracost dashboard or pull request comment, with greater impact in workflows that provide repository secrets. This issue is fixed in version 0.10.45.

CVSS v3
5.9
EG Score
5.9MEDIUMmedium confidence
EG Risk
27
EG Risk 27/100

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 (value × EchelonGraph’s weight)
Severity59% × 45%
The EG Score, 5.9 of 10.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
44th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 21, 2026

Last Modified

September 18, 2026

Advisory Details (4)

Auto-updated Aug 21, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
GitHub advisoryMentions a patch (unverified)

Arbitrary file read via config-template readFile symlink traversal · Advisory · infracost/infracost · GitHub

https://github.com/infracost/infracost/security/advisories/GHSA-mmg6-4qmv-6pc8
GitHub release Patch Available

v0.10.45

Patch available: infracost/infracost v0.10.45

https://github.com/infracost/infracost/releases/tag/v0.10.45
GitHub pull request

fix(security): resolve intermediate symlinks in path confinement

Fix merged in infracost/infracost PR #3586 on 2026-06-26 — awaiting tagged release

https://github.com/infracost/infracost/pull/3586
GitHub commit

commit 4d39331afc0e (infracost/infracost)

Fix landed in infracost/infracost commit 4d39331afc0e — awaiting tagged release

https://github.com/infracost/infracost/commit/4d39331afc0e27752d16d9d91c34583e5e8487fb

Vendor Advisories for CVE-2026-71493(1)

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

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/infracost/infracost—
  • every version up to 0.10.45: fixed in 0.10.45
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 49× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  3. 2026-10-12 15:42 UTCEG score recompute
  4. 2026-10-11 19:28 UTCEG score recompute
  5. 2026-10-11 16:43 UTCEG score recompute
  6. 2026-10-11 14:03 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  10. 2026-10-09 06:06 UTCEG score recompute
  11. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  12. 2026-10-08 05:05 UTCEG score recompute
  13. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  14. 2026-10-07 04:05 UTCEG score recompute
  15. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  16. 2026-10-06 03:04 UTCEG score recompute
  17. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  18. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  19. 2026-10-03 16:42 UTCEG score recompute
  20. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  21. 2026-10-02 09:52 UTCEG score recompute
  22. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  23. 2026-10-01 08:53 UTCEG score recompute
  24. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  25. 2026-09-30 07:52 UTCEG score recompute
Show 62 more
  1. 2026-09-29 04:27 UTCEG score recompute
  2. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  3. 2026-09-28 03:27 UTCEG score recompute
  4. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  5. 2026-09-27 02:28 UTCEG score recompute
  6. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  7. 2026-09-25 02:17 UTCEG score recompute
  8. 2026-09-24 01:16 UTCEG score recompute
  9. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  10. 2026-09-23 00:17 UTCEG score recompute
  11. 2026-09-21 23:17 UTCEG score recompute
  12. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  13. 2026-09-20 22:17 UTCEG score recompute
  14. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  15. 2026-09-19 21:17 UTCEG score recompute
  16. 2026-09-18 20:17 UTCEG score recompute
  17. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  18. 2026-09-18 11:39 UTCEG score recompute
  19. 2026-09-17 10:37 UTCEG score recompute
  20. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  21. 2026-09-16 09:36 UTCEG score recompute
  22. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  23. 2026-09-15 07:47 UTCEG score recompute
  24. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  25. 2026-09-14 06:47 UTCEG score recompute
  26. 2026-09-13 05:47 UTCEG score recompute
  27. 2026-09-12 15:02 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  28. 2026-09-12 04:47 UTCEG score recompute
  29. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  30. 2026-09-11 03:46 UTCEG score recompute
  31. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  32. 2026-09-09 01:46 UTCEG score recompute
  33. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  34. 2026-09-07 10:18 UTCEG score recompute
  35. 2026-09-06 13:48 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  36. 2026-09-06 09:17 UTCEG score recompute
  37. 2026-09-05 08:11 UTCEG score recompute
  38. 2026-09-04 07:11 UTCEG score recompute
  39. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  40. 2026-09-03 06:11 UTCEG score recompute
  41. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  42. 2026-09-02 05:11 UTCEG score recompute
  43. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  44. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  45. 2026-08-31 03:08 UTCEG score recompute
  46. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  47. 2026-08-30 02:08 UTCEG score recompute
  48. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  49. 2026-08-29 01:07 UTCEG score recompute
  50. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  51. 2026-08-27 19:24 UTCEG score recompute
  52. 2026-08-26 18:24 UTCEG score recompute
  53. 2026-08-26 18:07 UTCEG score recompute
  54. 2026-08-26 14:47 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  55. 2026-08-25 22:30 UTCEG score recompute
  56. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  57. 2026-08-24 21:29 UTCEG score recompute
  58. 2026-08-23 20:17 UTCEG score recompute
  59. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  60. 2026-08-21 18:18 UTCEG score recompute
  61. 2026-08-21 18:04 UTCEG score recomputeFirst assessed: 5.9 MEDIUM
  62. 2026-08-21 18:04 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Same product

1 shown

Go:github.com/infracost/infracost

Frequently asked(5)

What is CVE-2026-71493?
CVE-2026-71493 is a medium-severity vulnerability; its CVE record was published on August 21, 2026. Infracost provides cloud cost intelligence for engineers, AI coding agents, and CI/CD. Prior to 0.10.45, the readFile, pathExists, isDir, and matchPaths template functions in internal/config/template/parser.go use a lexical filepath.Rel check and a leaf-only os.Lstat check that do not resolve an…
When was the CVE record for CVE-2026-71493 published?
The CVE record for CVE-2026-71493 was published on August 21, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 18, 2026; the record at its source may have been updated since.
Is CVE-2026-71493 actively exploited?
CVE-2026-71493 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-71493?
CVE-2026-71493 has a CVSS base score of 5.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-71493?
A fix for CVE-2026-71493 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-71493 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-71493

Explore →

Is Your Infrastructure Affected by CVE-2026-71493?

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

Book a Demo →Browse All CVEs