← back to feed
CVE-2026-118383

CVE-2026-118383

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

EUVD-2026-122846 ↗

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 Server >= 9.0.0, < 9.0.7; >= 8.3.0, < 8.3.16; >= 8.0.0, < 8.0.37; >= 7.0.0, < 7.0.48; >= 6.0.0, < 6.0.30; >= 5.0.0, < 5.0.35; >= 4.4.0, < 4.4.32
fixed in 9.0.7, 8.3.16, 8.0.37, 7.0.48, 6.0.30, 5.0.35, 4.4.32
CWE-416 Use After Free
ETK-2026-4097Zero's internal tracking ID, independent of the CVE number., permanent identifier
cvss9.5cna vendorCVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
9h 20msince last run
33mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h02m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

MongoDB Server replica-set members can encounter a use-after-free while a newly elected primary completes replication catch-up. Unauthenticated requests may trigger a server crash and, in some circumstances, code execution in the database server process; standalone mongod deployments are not affected.

mitigation

Upgrade affected MongoDB Server deployments to 9.0.7, 8.3.16, 8.0.37, 7.0.48, 6.0.30, 5.0.35, or 4.4.32, as applicable. Prioritize replica-set members, including shard and config-server replica sets.

fixed in 9.0.7, 8.3.16, 8.0.37, 7.0.48, 6.0.30, 5.0.35, 4.4.32

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.
–
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
33m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-10 20:23Z
Δ 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

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

  1. 2026-11-10 20:23Z
    cve_org: trigger signal, started the run
    https://www.cve.org/CVERecord?id=CVE-2026-118383

this entry in the feed

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

{
  "etk_id": "ETK-2026-4097",
  "cve_id": "CVE-2026-118383",
  "display_id": "CVE-2026-118383",
  "ghsa_id": null,
  "euvd_id": "EUVD-2026-122846",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Pre-authentication use-after-free in MongoDB Server replication",
  "summary": "MongoDB Server replica-set members can encounter a use-after-free while a newly elected primary completes replication catch-up. Unauthenticated requests may trigger a server crash and, in some circumstances, code execution in the database server process; standalone mongod deployments are not affected.",
  "mitigation": "Upgrade affected MongoDB Server deployments to 9.0.7, 8.3.16, 8.0.37, 7.0.48, 6.0.30, 5.0.35, or 4.4.32, as applicable. Prioritize replica-set members, including shard and config-server replica sets.",
  "vendor": "MongoDB",
  "product": "MongoDB Server",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 9.0.0, < 9.0.7",
        ">= 8.3.0, < 8.3.16",
        ">= 8.0.0, < 8.0.37",
        ">= 7.0.0, < 7.0.48",
        ">= 6.0.0, < 6.0.30",
        ">= 5.0.0, < 5.0.35",
        ">= 4.4.0, < 4.4.32"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "9.0.7",
        "8.3.16",
        "8.0.37",
        "7.0.48",
        "6.0.30",
        "5.0.35",
        "4.4.32"
      ],
      "package_name": "MongoDB Server",
      "purl": null
    }
  ],
  "cwes": [
    416
  ],
  "cvss_score": 9.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 32.9743421,
  "t0_at": "2026-11-10T20:23:51.424000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-10T20:23:51.424000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-10T20:23:51.424000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-118383"
    }
  }
}

published 2026-11-10 20:52Z
last change 2026-11-11 05:12Z

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.

Protected by reCAPTCHA; the Google Privacy Policy and Terms of Service apply.