dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-3820

HIGH · 7.2 CVSS v3.1 Published 2026-06-04
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
There is a vulnerability in the Supermicro BMC SMTP service at Supermicro AS-2115HS-TNR.  An attacker may obtain administrator privileges and inject specially crafted characters into the SMTP service configuration. This may cause the underlying system to execute unintended commands during process invocation. Potential impact includes denial-of-service attacks, arbitrary code execution, or permanent compromise of the controller.

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

A command injection vulnerability in the Supermicro BMC SMTP service (AS-2115HS-TNR) allows an authenticated attacker with administrator privileges to inject specially crafted characters into the SMTP service configuration, causing the underlying system to execute unintended commands during process invocation.

MitigationRestrict BMC management interface access to trusted networks, limit SMTP configuration privileges to essential personnel only, and apply vendor-supplied firmware patches when 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 the BMC model
    Access the BMC web interface or run IPMI commands (ipmitool -I lanplus -H <BMC-IP> -U admin raw commands) to retrieve the system model (e.g., AS-2115HS-TNR) and firmware version
    Affected if The system is a Supermicro BMC, particularly the AS-2115HS-TNR model or similar Supermicro BMC platforms with SMTP configuration capability
  2. Verify SMTP service is enabled
    Log into the BMC web interface and navigate to: Maintenance > SMTP Settings or use IPMI: ipmitool -I lanplus -H <BMC-IP> -U admin raw 0x32 0x39 to check SMTP configuration status
    Affected if SMTP service is enabled and configured in the BMC
  3. Check SMTP configuration for injection points
    Review SMTP settings (Server Address, Port, Sender Email, Recipient Emails, Authentication credentials) via BMC web interface or IPMI for unusual characters such as semicolons, pipes, backticks, $(...), or other shell metacharacters
    Affected if Any SMTP configuration field contains shell metacharacters (;, |, `, $(, >, <, &) that were not intentionally configured by the administrator
  4. Audit BMC administrator accounts
    List all BMC user accounts with administrator privileges via IPMI: ipmitool -I lanplus -H <BMC-IP> -U admin user list or via BMC web interface under User Management
    Affected if There are unauthorized or unexpected administrator accounts, indicating potential compromise
  5. Review BMC logs for command injection evidence
    Extract BMC event logs via IPMI: ipmitool -I lanplus -H <BMC-IP> -U admin sel elist or check BMC web interface logs for entries related to SMTP configuration changes and unexpected process spawns
    Affected if Logs show SMTP configuration changes or process executions that do not match legitimate administrative actions

The environment is affected if the system is a Supermicro BMC (particularly AS-2115HS-TNR) with SMTP service enabled, and the SMTP configuration fields contain shell metacharacters or the logs show unexplained SMTP-related process executions.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict BMC management interface access to trusted networks, limit SMTP configuration privileges to essential personnel only, and apply vendor-supplied firmware patches when available.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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