CVE-2026-78861

validatedZero produced an exploit or a check.

GHSA-4jgr-x73g-p576 ↗EUVD-2026-92785 ↗

check availableZero validated a working check for it.proven exploitableZero has validated a full working exploit.
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.
Mercusys AC12 V2 n/a
CWE-789 Memory Allocation with Excessive Size Value
ETK-2026-723, permanent identifier
+1.2dTTV
16mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0hcheck + exploit+29h08m
0
+6h
+12h
+18h
+24h

description

Mercusys AC12 V2 contains a hardcoded 512-bit RSA private key. An attacker with local access may be able to execute code on the device.

mitigation

Restrict local access to the router to trusted administrators and place it on a controlled network segment. Monitor Mercusys for updated firmware and apply a vendor-provided fix when available.

check
available
exploit
yes
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.
deterministic
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.14%2nd percentile
agent run time
16m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-05 00:00Z
Δ 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

Differential: the exploit fired on the vulnerable build and stayed silent on the patched one.

source signals

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

  1. 2026-10-05 00:00Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-78861

{
  "etk_id": "ETK-2026-723",
  "cve_id": "CVE-2026-78861",
  "display_id": "CVE-2026-78861",
  "ghsa_id": "GHSA-4jgr-x73g-p576",
  "euvd_id": "EUVD-2026-92785",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Hardcoded RSA private key in Mercusys AC12 V2",
  "summary": "Mercusys AC12 V2 contains a hardcoded 512-bit RSA private key. An attacker with local access may be able to execute code on the device.",
  "mitigation": "Restrict local access to the router to trusted administrators and place it on a controlled network segment. Monitor Mercusys for updated firmware and apply a vendor-provided fix when available.",
  "vendor": "Mercusys",
  "product": "Mercusys AC12 V2",
  "affected": [
    {
      "affected_notes": [
        "n/a"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "n/a",
      "purl": null
    }
  ],
  "cwes": [
    789
  ],
  "cvss_score": 7.7,
  "cvss_src": "nvd",
  "cvss_vector": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N",
  "epss_score": 0.0014,
  "epss_percentile": 0.0273,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "differential",
  "exploit": true,
  "pipeline_minutes": 16.3411213,
  "t0_at": "2026-10-05T00:00:00+00:00",
  "signals": {
    "check": {
      "at": "2026-10-06T05:08:11.824139+00:00",
      "days": 1.214025742349537,
      "is_lower_bound": false,
      "measured_at": "2026-10-05T00:00:00+00:00",
      "url": null
    },
    "exploit": {
      "at": "2026-10-06T05:08:11.824139+00:00",
      "days": 1.214025742349537,
      "is_lower_bound": false,
      "measured_at": "2026-10-05T00:00:00+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-05T00:00:00+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-05T00:00:00+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-78861"
    }
  }
}

published 2026-10-06 04:51Z
last change 2026-10-21 09:20Z

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.