CVE-2026-48394

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-28. The CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
Trending — 3 sources updated this week
7.8EG
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.3%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

Bridge is affected by an out-of-bounds write vulnerability that could result in arbitrary code execution in the context of the current user. Exploitation of this issue requires user interaction in that a victim must open a malicious file.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/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)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.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 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 referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
0.3%
EPSS %ILE
16th
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.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-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-10-17). 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 low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 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 low or medium mission impact; Track* at high (mission-essential systems).

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

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

July 28, 2026

Last Modified

August 27, 2026

References (1)

Vendor Advisories for CVE-2026-48394(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 10× in last 7d / 55× 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 249 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 149 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-48394?
CVE-2026-48394 is a high-severity vulnerability; its CVE record was published on July 28, 2026. Bridge is affected by an out-of-bounds write vulnerability that could result in arbitrary code execution in the context of the current user. Exploitation of this issue requires user interaction in that a victim must open a malicious file.
When was CVE-2026-48394 made public?
CVE-2026-48394 was made public on July 28, 2026: that is the date its CVE record's CNA, Adobe Systems Incorporated, gives for when the vulnerability was made public. The CVE record itself was published on July 28, 2026. EchelonGraph's copy of the record carries a last-modified date of August 27, 2026; the record at its source may have been updated since.
Is CVE-2026-48394 actively exploited?
CVE-2026-48394 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (16th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-48394?
CVE-2026-48394 has a CVSS base score of 7.8 (the CNA's own assessment, by adobe; NVD's own analysis pending).
How do I remediate CVE-2026-48394?
A fix for CVE-2026-48394 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation. The vendor advisories EchelonGraph has for CVE-2026-48394 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-48394?

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