Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-77751 – Path Traversal Leading to Arbitrary File Disclosure – MISP misp-stix ≤ 2026.7.8

Be the first to know when new zero-days emerge:

Summary

CVE-2026-77751 is a path traversal vulnerability (CWE-22) in misp-stix, the STIX 2 import/export component of the MISP threat intelligence platform. It affects handling of object template names during STIX 2 import and MISP-to-STIX 2 export, and carries a HIGH severity score of 8.8. A remote, unauthenticated attacker can craft a malicious object name to escape the intended template directory and cause disclosure of local files accessible to the MISP process.

Technical details

  • Root cause: Object template names supplied in STIX/MISP content are joined directly into a filesystem path (template directory + object name + definition.json) without restricting the name to a safe, single path component.
  • Trigger conditions: An attacker-controlled object name (e.g., a custom STIX object’s x_misp_name field) containing path separators or ../ traversal sequences reaches the template-resolution logic during STIX 2 import.
  • Persistence risk: A malicious object name can be stored in a MISP event and later reprocessed during STIX 2 export, meaning content introduced under one security context can trigger file access later, potentially under a different or more privileged process.
  • Attack vector: Network — no authentication or user interaction required beyond submitting/importing crafted STIX content.
  • Impact: Disclosure of arbitrary local definition.json-style files accessible to the process, whose contents may be interpreted as a template and copied into the converted object, along with modification of the resulting object’s metadata/semantics.

Affected software

  • MISP misp-stix component: versions 0 through 2026.7.8 (all versions prior to the fix)

Severity

  • CVSS Score: 8.8 (High)
  • Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade misp-stix to a version that includes the fix applied in commits a8b6808d and a0f54070, which validate object template names against a safe pattern (letters, digits, hyphens, underscores only) and route invalid names to a generic unknown-template object instead of resolving them from the filesystem.
  • If immediate patching is not possible: Restrict which users/systems can submit STIX 2 content for import, and monitor MISP logs for objects converted to unknown-template or template resolution warnings, which may indicate attempted exploitation. Limit filesystem permissions available to the MISP/misp-stix process to reduce the impact of any successful traversal.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge