CVE-2026-121382

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

GHSA-c894-38h9-3f4g ↗EUVD-2026-116139 ↗

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.
Netcore NBR100V2 1.3.240614.030928
CWE-190 Integer Overflow or Wraparound
ETK-2026-3397Zero's internal tracking ID, independent of the CVE number., permanent identifier
1d 02h 11msince last run
15mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+3h33m
0
+2h
+6h
+8h
+10h
+12h

description

Netcore NBR100V2 devices running firmware 1.3.240614.030928 are affected by an integer overflow in the auto_ac service. A remote attacker may be able to disrupt device availability without credentials if they can reach the vulnerable service.

mitigation

Restrict access to the device and its management-facing services to trusted administrator networks, and block untrusted remote access. Monitor the vendor for a corrected firmware release; no fixed version is recorded in the available advisory data.

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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
15m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-03 18:45Z
Δ 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-03 18:45Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3397",
  "cve_id": "CVE-2026-121382",
  "display_id": "CVE-2026-121382",
  "ghsa_id": "GHSA-c894-38h9-3f4g",
  "euvd_id": "EUVD-2026-116139",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Integer overflow in Netcore NBR100V2 auto_ac service",
  "summary": "Netcore NBR100V2 devices running firmware 1.3.240614.030928 are affected by an integer overflow in the auto_ac service. A remote attacker may be able to disrupt device availability without credentials if they can reach the vulnerable service.",
  "mitigation": "Restrict access to the device and its management-facing services to trusted administrator networks, and block untrusted remote access. Monitor the vendor for a corrected firmware release; no fixed version is recorded in the available advisory data.",
  "vendor": "Netcore",
  "product": "NBR100V2",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "1.3.240614.030928"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "NBR100V2",
      "purl": null
    }
  ],
  "cwes": [
    190
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:P",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 15.26645045,
  "t0_at": "2026-11-03T18:45:19.264000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-03T18:45:19.264000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-03T18:45:19.264000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-121382"
    }
  }
}

published 2026-11-03 19:16Z
last change 2026-11-04 01:56Z

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.