dbcve.org
Command InjectionWeakness · CWE-77

CVE-2026-8431

HIGH · 7.2 CVSS v3.1 Published 2026-05-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
An administrative user with access to configure webhooks can execute arbitrary commands by configuring and then triggering webhooks containing specific FreeMarker template syntax.  This issue affects all MongoDB Ops Manager 7.0 versions and MongoDB Ops Manager versions 8.0.22 and prior.

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 · high confidence

Authenticated administrative users with webhook configuration privileges can achieve remote code execution by injecting FreeMarker template syntax into webhook configurations, which are then evaluated server-side during webhook triggering.

MitigationRestrict webhook configuration permissions to only trusted admins, and upgrade to the latest MongoDB Ops Manager version once the patch is available.

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

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/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. Identify Ops Manager installation and version
    Locate the MongoDB Ops Manager installation and retrieve its version number using the Ops Manager UI or API, or check system packages/processes for the installed version
    Affected if The installed version falls within any affected version range for this CVE (check against official MongoDB security advisories)
  2. Verify webhook feature is enabled
    Check if webhooks are configured in the Ops Manager administration settings, typically found in the Automation, Backup, or Monitoring configuration sections under webhook settings
    Affected if Webhooks are enabled and configured in the Ops Manager instance
  3. Review webhook configurations for template syntax
    Inspect all webhook configurations stored in the Ops Manager database or configuration files, looking for FreeMarker template markers such as ${, <#, <@, or other template directives that could indicate injection
    Affected if Any webhook configuration contains FreeMarker template syntax that was not intentionally configured by an administrator
  4. Check admin user permissions for webhooks
    Review administrative user roles and permissions in Ops Manager, specifically identifying users granted webhook configuration or modification privileges
    Affected if Multiple untrusted administrators have webhook configuration permissions beyond those explicitly required for operations

You are affected if MongoDB Ops Manager is running an unpatched version AND webhooks are enabled AND an attacker with webhook configuration privileges has injected FreeMarker template syntax into webhook settings.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict webhook configuration permissions to only trusted admins, and upgrade to the latest MongoDB Ops Manager version once the patch is available.

Recommended fix Moderate confidence

Ops Manager 8.0.23 or later (for 8.0.x users); contact MongoDB Support for 7.0.x patches

  1. 1. Identify the current MongoDB Ops Manager version by checking the Ops Manager UI or running: `db.version()` in the Ops Manager application database
  2. 2. For Ops Manager 8.0.x: Upgrade to Ops Manager 8.0.23 or later, which contains the fix for this vulnerability
  3. 3. For Ops Manager 7.0.x: Contact MongoDB Support to obtain a patched version, as the description indicates all 7.0 versions are affected
  4. 4. After upgrading, verify the Ops Manager version matches the expected fixed release
  5. 5. Restrict administrative access to webhook configuration to only trusted users as an additional precaution
  6. 6. Review existing webhook configurations for any malicious FreeMarker template syntax and remove if found
Caveat Review MongoDB upgrade documentation for any migration requirements between minor versions

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8431 — 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-8431 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