dbcve.org
MongoDBDatabase / datastore

CVE-2026-1848

HIGH · 7.5 CVSS v3.1 Published 2026-02-10
Fix available
A fix is available. Upgrade to 7.0.29 / 8.0.18 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Connections received from the proxy port may not count towards total accepted connections, resulting in server crashes if the total number of connections exceeds available resources. This only applies to connections accepted from the proxy port, pending the proxy protocol header.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Connections received from the proxy port are not being tracked in the total accepted connection count. When connections arrive on the proxy port and await proxy protocol header parsing, they bypass the connection limit enforcement mechanism. If the total number of connections (including untracked proxy connections) exceeds available server resources, the server crashes due to resource exhaustion.

MitigationImplement proper connection tracking for all connections received on the proxy port before the proxy protocol header is processed, ensuring they count toward the total accepted connection limit.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MongoDBDatabase / datastore
Affected:>= 7.0.0, < 7.0.29>= 8.0.0, < 8.0.18>= 8.2.0, < 8.2.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check MongoDB server version
    Run `mongod --version` or connect to the database and run `db.version()` to get the installed version number
    Affected if The installed version falls within one of these ranges: >= 7.0.0 and < 7.0.29; >= 8.0.0 and < 8.0.18; >= 8.2.0 and < 8.2.4
  2. Locate MongoDB configuration file
    Find the mongod.conf file (typically at /etc/mongod.conf or /etc/mongodb.conf depending on installation)
    Affected if Configuration file exists on the system
  3. Check if proxy protocol is enabled
    Inspect the configuration file for `net.proxyProtocol` settings. Look for a section under `net:` that includes `proxyProtocol: enabled` or similar proxy protocol configuration
    Affected if Proxy protocol is enabled in the MongoDB configuration (net.proxyProtocol is set to enabled or a listen address is configured for proxy protocol)
  4. Check for active proxy port listeners
    Run `ss -tlnp` or `netstat -tlnp` to list listening ports, then check if any port is configured to accept proxy protocol connections. Review mongod logs for proxy protocol related entries
    Affected if A proxy protocol listening port is active and accepting connections

You are affected if your MongoDB version is within the affected ranges AND proxy protocol is enabled with an active listener, as connections on the proxy port bypass connection tracking leading to potential resource exhaustion.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.0.29 / 8.0.18 / 8.2.4 or later
Fixed in 7.0.298.0.188.2.4
Interim mitigation

Implement proper connection tracking for all connections received on the proxy port before the proxy protocol header is processed, ensuring they count toward the total accepted connection limit.

Recommended fix High confidence

MongoDB 7.0.29+ (for 7.0.x), 8.0.18+ (for 8.0.x), or 8.2.4+ (for 8.2.x)

  1. 1. Backup your MongoDB data and configuration files before upgrading
  2. 2. Schedule a maintenance window for the upgrade
  3. 3. For 7.0.x users: Upgrade to MongoDB 7.0.29 or later (recommended: latest 7.0.x stable)
  4. 4. For 8.0.x users (excluding 8.2.x): Upgrade to MongoDB 8.0.18 or later (recommended: latest 8.0.x stable)
  5. 5. For 8.2.x users: Upgrade to MongoDB 8.2.4 or later (recommended: latest 8.2.x stable)
  6. 6. After upgrade, restart the MongoDB service
  7. 7. Verify the upgrade was successful by checking mongod logs for version and ensuring no errors
  8. 8. Test that connections via proxy protocol are now properly counted toward the connection limit
Caveat Standard upgrade precautions apply; review MongoDB upgrade documentation for your specific version jump for any migration requirements

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in MongoDB Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1848 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-1848 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data