CVE-2026-77751

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7% (50th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
8.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 8.8Exploit: None knownExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

A path traversal vulnerability existed in the handling of MISP object template names during STIX 2 import and MISP-to-STIX 2 export.

MISP object names are passed to PyMISP's object-template resolution mechanism, which constructs a filesystem path by joining the configured MISP object-template directory, the object name, and definition.json. An object name originating from untrusted STIX or MISP content was not sufficiently restricted before being used in this filesystem path.

An attacker able to supply a crafted object name containing path separators or traversal sequences such as ../ could therefore cause template resolution to escape the expected template directory and attempt to load a definition.json file from another location accessible to the process.

During STIX 2 import, an attacker-controlled x_misp_name from a custom STIX object could directly reach this template-resolution mechanism.

The issue could also become persistent. A malicious object name stored in a MISP event could later be processed again during STIX 2 export. Consequently, content originally introduced in one security context could trigger filesystem access later when the event is exported by a process operating with different or greater privileges.

If a suitable definition.json file exists outside the intended template directory, its contents may be interpreted as a MISP object template and fields from that file copied into the converted object. This can result in unintended disclosure of locally accessible data represented by the template file and modification of the resulting object's metadata or semantics.

The patches introduce strict validation of object-template names. Valid names are restricted to a single path component containing letters, digits, hyphens, or underscores. Names that do not meet these requirements are replaced with the generic unknown-template name before reaching PyMISP template resolution. The original rejected name is preserved in the object's comment and a warning is generated, preventing traversal while retaining the source information.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
55
EG Risk 55/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)
Severity88% × 45%
The EG Score, 8.8 of 10.
Exploitation1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high until it ships, then apply the release.
EPSS PROB
0.7%
EPSS %ILE
50th
KEV
Not listed

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

An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high until it ships, then apply the release.

Exploitation none (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

August 21, 2026

Last Modified

August 26, 2026

Advisory Details (2)

Auto-updated Aug 21, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
github_commit

commit a0f54070 (MISP/misp-stix)

Fix landed in MISP/misp-stix commit a0f54070 — awaiting tagged release

https://github.com/MISP/misp-stix/commit/a0f54070
github_commit

commit a8b6808d (MISP/misp-stix)

Fix landed in MISP/misp-stix commit a8b6808d — awaiting tagged release

https://github.com/MISP/misp-stix/commit/a8b6808d

Vendor Advisories for CVE-2026-77751(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 21× in last 7d / 98× 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 99 of 183 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 84 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-77751?
CVE-2026-77751 is a high-severity vulnerability; its CVE record was published on August 21, 2026. A path traversal vulnerability existed in the handling of MISP object template names during STIX 2 import and MISP-to-STIX 2 export. MISP object names are passed to PyMISP's object-template resolution mechanism, which constructs a filesystem path by joining the configured MISP object-template…
When was the CVE record for CVE-2026-77751 published?
The CVE record for CVE-2026-77751 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 August 26, 2026; the record at its source may have been updated since.
Is CVE-2026-77751 actively exploited?
CVE-2026-77751 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (50th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-77751?
CVE-2026-77751 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-77751?
An upstream fix for CVE-2026-77751 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-77751 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-77751?

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