CVE-2026-104845

validatedZero produced an exploit or a check.

GHSA-jp82-f5mq-hwhp ↗EUVD-2026-91744 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
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.
lxsmnsyc seroval <= 1.6.2
fixed in 1.6.3
CWE-770 Allocation of Resources Without Limits or Throttling
ETK-2026-396, permanent identifier
pkg:npm/seroval
+9h52mTTV
12mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0hcheck available+9h52magent stopped
0
+2h
+4h
+6h
+8h

description

Seroval versions before 1.6.3 can consume excessive memory or CPU when deserializing crafted typed-array data. An attacker must be able to supply untrusted JSON to the affected Seroval deserialization paths, which can block the event loop and degrade availability.

mitigation

Upgrade seroval to version 1.6.3 or later. Until upgraded, avoid passing untrusted JSON to Seroval deserialization functions.

fixed in 1.6.3

check
available
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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.43%36th percentile
agent run time
12m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-02 15:55Z
Δ 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

Mechanism verified: the exploit fired on the vulnerable build and stayed silent on the patched one, but the server it ran against was ours, so no check ships for it.

source signals

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

  1. 2026-10-02 15:55Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-396",
  "cve_id": "CVE-2026-104845",
  "display_id": "CVE-2026-104845",
  "ghsa_id": "GHSA-jp82-f5mq-hwhp",
  "euvd_id": "EUVD-2026-91744",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unchecked typed-array deserialization resource exhaustion in seroval",
  "summary": "Seroval versions before 1.6.3 can consume excessive memory or CPU when deserializing crafted typed-array data. An attacker must be able to supply untrusted JSON to the affected Seroval deserialization paths, which can block the event loop and degrade availability.",
  "mitigation": "Upgrade seroval to version 1.6.3 or later. Until upgraded, avoid passing untrusted JSON to Seroval deserialization functions.",
  "vendor": "lxsmnsyc",
  "product": "seroval",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 1.6.2"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        "1.6.3"
      ],
      "package_name": "seroval",
      "purl": "pkg:npm/seroval"
    }
  ],
  "cwes": [
    770
  ],
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
  "epss_score": 0.0043,
  "epss_percentile": 0.3608,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "mechanism_verified",
  "exploit": false,
  "pipeline_minutes": 12.434300666666667,
  "t0_at": "2026-10-02T15:55:21.197000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-03T01:46:57.366464+00:00",
      "days": 0.41083529472222224,
      "is_lower_bound": false,
      "measured_at": "2026-10-02T15:55:21.197000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-02T15:55:21.197000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-02T15:55:21.197000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-104845"
    }
  }
}

published 2026-10-03 01:34Z
last change 2026-10-21 10:52Z

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.