CVE-2026-5473

HIGHNVD 7.07.0
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.0 under NVD CVSS v3. EPSS exploit probability: 0.2% (12th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 4.5 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-04-03) is not newer than that change (2026-07-24), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2026-18805 (ENISA EUVD) · GHSA-crxq-rm37-648f (GitHub Security Advisories)Source: ENISA EUVD

7.0EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.0Exploit: None knownExposed services: Not assessed

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

The CVE record's description, written by its CNA (VulDB), states the affected versions: "A vulnerability has been found in NASA cFS up to 7.0.0." No release containing a fix is confirmed on record.

A vulnerability has been found in NASA cFS up to 7.0.0. The impacted element is the function pickle.load of the component Pickle Module. Such manipulation leads to deserialization. The attack needs to be performed locally. The attack requires a high level of complexity. The exploitability is regarded as difficult. The exploit has been disclosed to the public and may be used. The project was informed of the problem early through an issue report but has not responded yet.

CVSS v3
7.0
EG Score
7.0HIGHmedium confidence
EG Risk
32
EG Risk 32/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)
Severity70% × 45%
Impact severity (EG Severity): CVSS 7.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 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: No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines, and watch for a fix.
EPSS PROB
0.2%
EPSS %ILE
12th
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 (7.0): severity, escalated by confirmed exploitation. This CVE's 7.0 is its impact severity (EG Severity), not escalated.

EG Severity
7.0 HIGHCVSS-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.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). 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: the SSVC and BOD 26-04 blocks below.

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

No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines, and watch for a fix.

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.

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

April 3, 2026

Last Modified

July 24, 2026

Advisory Details (2)

Auto-updated May 1, 2026
No fix on record yet.
Web page

[SECURITY] pickle.load() arbitrary code execution in cFS-GroundSystem · Issue #951 · nasa/cFS · GitHub

https://github.com/nasa/cFS/issues/951
Web page

GitHub - nasa/cFS: The Core Flight System (cFS) · GitHub

https://github.com/nasa/cFS/

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 43× 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 100 of 234 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. None are among the latest 100 rows. The 134 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-5473?
CVE-2026-5473 is a high-severity vulnerability; its CVE record was published on April 3, 2026. A vulnerability has been found in NASA cFS up to 7.0.0. The impacted element is the function pickle.load of the component Pickle Module. Such manipulation leads to deserialization. The attack needs to be performed locally. The attack requires a high level of complexity. The exploitability is…
When was the CVE record for CVE-2026-5473 published?
The CVE record for CVE-2026-5473 was published on April 3, 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 July 24, 2026; the record at its source may have been updated since.
Is CVE-2026-5473 actively exploited?
CVE-2026-5473 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (12th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-5473?
CVE-2026-5473 has a CVSS v3 base score of 7.0 (NVD).
How do I remediate CVE-2026-5473?
No fix for CVE-2026-5473 is confirmed yet. Until one is published, restrict network exposure of the affected system — for example, keep it off the internet or limit it to trusted networks — and watch for a fix. The CVE record's description, written by its CNA (VulDB), states the affected versions: "A vulnerability has been found in NASA cFS up to 7.0.0." No release containing a fix is confirmed on record.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-5473?

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

Book a Demo →Browse All CVEs