CVE-2026-126982

validatingZero is analyzing and reversing it now.

GHSA-vjj2-chwg-8r8c ↗

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.
MongoDB C# Driver
ETK-2026-4336Zero's internal tracking ID, independent of the CVE number., permanent identifier
–running
startingcurrent stage
timeline
0 = trigger signal
trigger signal (cve.org) +0h
0
+2h
+4h
+6h
+8h
+10h
+12h

description

MongoDB C# Driver applications that deserialize attacker-supplied or attacker-planted BSON or JSON into loosely typed polymorphic members are affected. An attacker may cause instantiation of .NET types outside the intended allow-list with attacker-controlled values, potentially leading to code execution where a suitable gadget type is present. The attacker must be able to introduce data that the application later deserializes.

Still under analysis: more detail becomes available as the pipeline runs.

mitigation

Do not deserialize untrusted BSON or JSON into loosely typed polymorphic members, and restrict who can introduce data consumed by these deserialization paths. Review affected applications for an applicable vendor update and deploy it when available.

check
building now
exploit
not yet
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.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
–
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-13 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

Run in progress: no artifact yet.

source signals

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

  1. 2026-11-13 00:00Z
    ghsa: trigger signal, started the run
  2. 2026-11-13 00:00Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-4336",
  "cve_id": "CVE-2026-126982",
  "display_id": "CVE-2026-126982",
  "ghsa_id": "GHSA-vjj2-chwg-8r8c",
  "euvd_id": null,
  "status": "in_pipeline",
  "anchor_state": "anchored",
  "title": "Type allow-list bypass in MongoDB C# Driver BSON deserialization",
  "summary": "MongoDB C# Driver applications that deserialize attacker-supplied or attacker-planted BSON or JSON into loosely typed polymorphic members are affected. An attacker may cause instantiation of .NET types outside the intended allow-list with attacker-controlled values, potentially leading to code execution where a suitable gadget type is present. The attacker must be able to introduce data that the application later deserializes.",
  "mitigation": "Do not deserialize untrusted BSON or JSON into loosely typed polymorphic members, and restrict who can introduce data consumed by these deserialization paths. Review affected applications for an applicable vendor update and deploy it when available.",
  "vendor": "MongoDB",
  "product": "C# Driver",
  "affected": [],
  "cwes": null,
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": null,
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": null,
  "t0_at": "2026-11-13T00:00:12.446000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-13T00:00:12.446000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-13T00:00:12.446000+00:00",
      "url": "https://github.com/advisories/GHSA-vjj2-chwg-8r8c"
    }
  }
}

published 2026-11-13 00:49Z
last change 2026-11-13 00:49Z

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.