CVE-2025-24278

CRITICALNVD 5.59.8
EchelonGraph scoreMEDIUM confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2025-04-01. NVD baseline CVSS 5.5; sources differ by 4.3.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2025-8941 (ENISA EUVD) · GHSA-jrgv-pmf9-6qg5 (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
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.5Exploit: None knownExposed services: Not assessed

The CVE record names the fixed release — apply it.

This issue was addressed with improved validation of symlinks. This issue is fixed in macOS Sequoia 15.4, macOS Sonoma 14.7.5, macOS Ventura 13.7.5. An app may be able to access protected user data.

CVSS v3
5.5
EG Score
9.8CRITICALmedium confidence
EG Risk
44
EG Risk 44/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 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: The CVE record names the fixed release. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
21st
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 (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-13). 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.

The CVE record names the fixed release. 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

March 31, 2025

Last Modified

July 23, 2026

Advisory Details (3)

Auto-updated Jul 26, 2026
Fix named in the CVE record.
Web page

About the security content of macOS Ventura 13.7.5 - Apple Support

https://support.apple.com/en-us/122375
Web page

About the security content of macOS Sonoma 14.7.5 - Apple Support

https://support.apple.com/en-us/122374
Web page

About the security content of macOS Sequoia 15.4 - Apple Support

https://support.apple.com/en-us/122373

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 60× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 298 rows 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 198 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-24278?
CVE-2025-24278 is a critical-severity vulnerability; its CVE record was published on March 31, 2025. This issue was addressed with improved validation of symlinks. This issue is fixed in macOS Sequoia 15.4, macOS Sonoma 14.7.5, macOS Ventura 13.7.5. An app may be able to access protected user data.
When was the CVE record for CVE-2025-24278 published?
The CVE record for CVE-2025-24278 was published on March 31, 2025. 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 23, 2026; the record at its source may have been updated since.
Is CVE-2025-24278 actively exploited?
CVE-2025-24278 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (21st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-24278?
CVE-2025-24278 has a CVSS v3 base score of 5.5 (NVD). EchelonGraph synthesises NVD + FIRST EPSS + GHSA into a combined EG score of 9.8 (CRITICAL).
How do I remediate CVE-2025-24278?
The CVE record for CVE-2025-24278 names the fix: "This issue is fixed in macOS Sequoia 15.4, macOS Sonoma 14.7.5, macOS Ventura 13.7.5."

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-24278

Explore →

Is Your Infrastructure Affected by CVE-2025-24278?

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

Book a Demo →Browse All CVEs