CVE-2025-66367

waiting for further signalsZero needs more public information before it can validate it.

GHSA-778h-c8h7-xwx4 ↗EUVD-2025-211264 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Samsung Semiconductor Exynos 850 >= 0, < July 2026
fixed in July 2026
CWE-125 Out-of-bounds Read
ETK-2026-3573Zero's internal tracking ID, independent of the CVE number., permanent identifier
3h 22msince last run
6mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+0h51m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

The flaw affects the listed Exynos processors, modems, and wearable platforms. An attacker able to cause a vulnerable device to process NAS DLTransport messages may crash the baseband.

mitigation

Install the July 2026 security update for affected devices and Exynos-based products. Prioritize devices that may process untrusted cellular-network traffic.

fixed in July 2026

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
6m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-05 02:37Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-05 02:37Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2025-66367

{
  "etk_id": "ETK-2026-3573",
  "cve_id": "CVE-2025-66367",
  "display_id": "CVE-2025-66367",
  "ghsa_id": "GHSA-778h-c8h7-xwx4",
  "euvd_id": "EUVD-2025-211264",
  "status": "published",
  "anchor_state": "anchored",
  "title": "NAS DLTransport handling flaw in Exynos baseband",
  "summary": "The flaw affects the listed Exynos processors, modems, and wearable platforms. An attacker able to cause a vulnerable device to process NAS DLTransport messages may crash the baseband.",
  "mitigation": "Install the July 2026 security update for affected devices and Exynos-based products. Prioritize devices that may process untrusted cellular-network traffic.",
  "vendor": "Samsung Semiconductor",
  "product": "Exynos 850",
  "affected": [
    {
      "affected_notes": [
        ">= 0, < July 2026"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [
        "July 2026"
      ],
      "package_name": "Exynos 850",
      "purl": null
    },
    {
      "affected_notes": [
        ">= 0, < July 2026"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [
        "July 2026"
      ],
      "package_name": "Exynos 2100",
      "purl": null
    },
    {
      "affected_notes": [
        ">= 0, < July 2026"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [
        "July 2026"
      ],
      "package_name": "Exynos 1280",
      "purl": null
    },
    {
      "affected_notes": [
        ">= 0, < July 2026"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [
        "July 2026"
      ],
      "package_name": "Exynos 2200",
      "purl": null
    },
    {
      "affected_notes": [
        ">= 0, < July 2026"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [
        "July 2026"
      ],
      "package_name": "Exynos 1330",
      "purl": null
    },
    {
      "affected_notes": [
        ">= 0, < July 2026"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [
        "July 2026"
      ],
      "package_name": "Exynos 1380",
      "purl": null
    },
    {
      "affected_notes": [
        ">= 0, < July 2026"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [
        "July 2026"
      ],
      "package_name": "Exynos 1480",
      "purl": null
    },
    {
      "affected_notes": [
        ">= 0, < July 2026"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [
        "July 2026"
      ],
      "package_name": "Exynos 2400",
      "purl": null
    },
    {
      "affected_notes": [
        ">= 0, < July 2026"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [
        "July 2026"
      ],
      "package_name": "Exynos 1580",
      "purl": null
    },
    {
      "affected_notes": [
        ">= 0, < July 2026"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [
        "July 2026"
      ],
      "package_name": "Exynos 2500",
      "purl": null
    },
    {
      "affected_notes": [
        ">= 0, < July 2026"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [
        "July 2026"
      ],
      "package_name": "Exynos 1680",
      "purl": null
    },
    {
      "affected_notes": [
        ">= 0, < July 2026"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [
        "July 2026"
      ],
      "package_name": "Exynos W920",
      "purl": null
    },
    {
      "affected_notes": [
        ">= 0, < July 2026"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [
        "July 2026"
      ],
      "package_name": "Exynos W930",
      "purl": null
    },
    {
      "affected_notes": [
        ">= 0, < July 2026"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [
        "July 2026"
      ],
      "package_name": "Exynos W1000",
      "purl": null
    },
    {
      "affected_notes": [
        ">= 0, < July 2026"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [
        "July 2026"
      ],
      "package_name": "Exynos Modem 5123",
      "purl": null
    },
    {
      "affected_notes": [
        ">= 0, < July 2026"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [
        "July 2026"
      ],
      "package_name": "Exynos Modem 5300",
      "purl": null
    },
    {
      "affected_notes": [
        ">= 0, < July 2026"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [
        "July 2026"
      ],
      "package_name": "Exynos Modem 5400",
      "purl": null
    },
    {
      "affected_notes": [
        ">= 0, < July 2026"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [
        "July 2026"
      ],
      "package_name": "Exynos Modem 5410",
      "purl": null
    }
  ],
  "cwes": [
    125
  ],
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 5.862784066666666,
  "t0_at": "2026-11-05T02:37:48.440000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-05T02:37:48.440000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-05T02:37:48.440000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2025-66367"
    }
  }
}

published 2026-11-05 03:22Z
last change 2026-11-05 04:37Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.