CVE-2024-47174

MEDIUMNVD 5.95.9
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 5.9 under NVD CVSS v3. EPSS exploit probability: 0.3% (22nd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3

Also known asEUVD-2024-42296 (ENISA EUVD)Source: ENISA EUVD

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.3%CVSS: 5.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Nix is a package manager for Linux and other Unix systems. Starting in version 1.11 and prior to versions 2.18.8 and 2.24.8, ` did not verify TLS certificates on HTTPS connections. This could lead to connection details such as full URLs or credentials leaking in case of a man-in-the-middle (MITM) attack. is also known as the builtin derivation builder builtin:fetchurl. It's not to be confused with the evaluation-time function builtins.fetchurl, which was not affected by this issue. A user may be affected by the risk of leaking credentials if they have a netrc file for authentication, or rely on derivations with impureEnvVars set to use credentials from the environment. In addition, the commonplace trust-on-first-use (TOFU) technique of updating dependencies by specifying an invalid hash and obtaining it from a remote store was also vulnerable to a MITM injecting arbitrary store objects. This also applied to the impure derivations experimental feature. Note that this may also happen when using Nixpkgs fetchers to obtain new hashes when not using the fake hash method, although that mechanism is not implemented in Nix itself but rather in Nixpkgs using a fixed-output derivation. The behavior was introduced in version 1.11 to make it consistent with the Nixpkgs pkgs.fetchurl and to make work in the derivation builder sandbox, which back then did not have access to the CA bundles by default. Nowadays, CA bundles are bind-mounted on Linux. This issue has been fixed in Nix 2.18.8 and 2.24.8. As a workaround, implement (authenticated) fetching with pkgs.fetchurl from Nixpkgs, using impureEnvVars and curlOpts` as needed.

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 impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity59% × 45%
Impact severity (EG Severity): CVSS 5.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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.3%
EPSS %ILE
22nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.9): severity, escalated by confirmed exploitation. This CVE's 5.9 is its impact severity (EG Severity), not escalated.

EG Severity
5.9 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (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

September 26, 2024

Last Modified

April 15, 2026

References (4)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntunix-setup-systemd (2.18.1+dfsg-1ubuntu5+esm2) @ noble2026-10-24ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
nix2.16.1+dfsg-1 ... 2.8.0-1.1 (31 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
nix2.16.1+dfsg-1 ... 2.8.0-1.1 (20 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
nix—
  • every version up to 2.24.8+dfsg-1: fixed in 2.24.8+dfsg-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
nix—
  • every version up to 2.24.8+dfsg-1: fixed in 2.24.8+dfsg-1
—

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 7× in last 7d / 37× 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.

Showing the most recent 94 of 221 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 6 repeat rows among the latest 100 are merged into the row they repeat. The 127 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:41 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  2. 2026-11-01 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  3. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  4. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  5. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  6. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  7. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  8. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  9. 2026-10-25 17:01 UTCEG score recompute
  10. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  11. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  12. 2026-10-24 04:32 UTCEG score recompute
  13. 2026-10-24 04:32 UTCVendor advisory
  14. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  15. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  16. 2026-10-21 16:30 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  17. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  18. 2026-10-19 16:30 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  19. 2026-10-18 06:58 UTCEG score recompute
  20. 2026-10-17 16:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  21. 2026-10-16 16:37 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  22. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  23. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  24. 2026-10-13 16:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  25. 2026-10-12 17:43 UTCEG score recompute
Show 69 more
  1. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  2. 2026-10-11 21:09 UTCEG score recompute
  3. 2026-10-11 16:01 UTCEG score recompute
  4. 2026-10-11 13:46 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  5. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  6. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  7. 2026-10-08 17:08 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  8. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  9. 2026-10-07 08:54 UTCOSV refresh
  10. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  11. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  12. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  13. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  14. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  15. 2026-09-30 19:54 UTCEG score recompute
  16. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  17. 2026-09-29 15:18 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  18. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  19. 2026-09-27 13:44 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  20. 2026-09-26 15:57 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  21. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  22. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  23. 2026-09-22 14:47 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  24. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  25. 2026-09-19 15:40 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  26. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  27. 2026-09-17 19:27 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  28. 2026-09-17 14:36 UTCOSV refresh
  29. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  30. 2026-09-16 05:12 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  31. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  32. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  33. 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  34. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  35. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  36. 2026-09-10 09:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  37. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  38. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  39. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  40. 2026-09-04 13:59 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  41. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  42. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  43. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  44. 2026-09-01 04:37 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  45. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  46. 2026-08-30 01:20 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  47. 2026-08-29 15:13 UTCOSV refresh
  48. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  49. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  50. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  51. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  52. 2026-08-24 14:15 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  53. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  54. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  55. 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  56. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  57. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  58. 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  59. 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  60. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  61. 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  62. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  63. 2026-08-13 02:31 UTCOSV refresh
  64. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  65. 2026-08-11 13:40 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  66. 2026-08-10 23:58 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  67. 2026-08-09 13:45 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  68. 2026-08-07 16:25 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  69. 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.3% · 21st percentile

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-47174?
CVE-2024-47174 is a medium-severity vulnerability; its CVE record was published on September 26, 2024. Nix is a package manager for Linux and other Unix systems. Starting in version 1.11 and prior to versions 2.18.8 and 2.24.8, <nix/fetchurl.nix> did not verify TLS certificates on HTTPS connections. This could lead to connection details such as full URLs or credentials leaking in case of a…
When was the CVE record for CVE-2024-47174 published?
The CVE record for CVE-2024-47174 was published on September 26, 2024. 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 April 15, 2026; the record at its source may have been updated since.
Is CVE-2024-47174 actively exploited?
CVE-2024-47174 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (22nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-47174?
CVE-2024-47174 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2024-47174?
A fix for CVE-2024-47174 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-47174

Explore →

Is Your Infrastructure Affected by CVE-2024-47174?

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

Book a Demo →Browse All CVEs