dbcve.org
JunosOperating system · Juniper

CVE-2026-33776

MEDIUM · 5.5 CVSS v3.1 Published 2026-04-09
Fix available
A fix is available. Upgrade to 22.4 / 23.2 or later.
See remediation →
57/100
Remediation priority · Elevated
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
A Missing Authorization vulnerability in the CLI of Juniper Networks Junos OS and Junos OS Evolved allows a local user with low privileges to read sensitive information. A local user with low privileges can execute the CLI command 'show mgd' with specific arguments which will expose sensitive information. This issue affects Junos OS: * all versions before 22.4R3-S8, * 23.2 versions before 23.2R2-S6, * 23.4 versions before 23.4R2-S6, * 24.2 versions before 24.2R2-S4, * 24.4 versions before 24.4R2-S1, * 25.2 version before 25.2R1-S2, 25.2R2; Junos OS Evolved: * all versions before 23.2R2-S6-EVO, * 23.4 version before 23.4R2-S6-EVO, * 24.2 version before 24.2R2-S4-EVO, * 24.4 versions before 24.4R2-S1-EVO, * 25.2 versions before 25.2R2-EVO.

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

A missing authorization vulnerability in the Junos OS and Junos OS Evolved CLI allows authenticated low-privilege local users to execute the 'show mgd' command with specific arguments to access sensitive information that should be restricted to higher privilege levels. The vulnerability stems from insufficient access control checks in the management daemon (mgd).

MitigationApply the vendor-provided Junos OS patches by upgrading to the fixed versions specified in the advisory. Until then, limit local CLI access and monitor for unauthorized 'show mgd' command usage.

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
JunosOperating system
Affected:< 22.4= 22.4= 23.2= 23.4= 24.2= 24.4= 25.2
Junos Os EvolvedOperating system
Affected:< 23.2= 23.2= 23.4= 24.2= 24.4= 25.2

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

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

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 installed Junos OS version
    Run 'show version' or 'request system version' command from CLI to obtain the exact Junos OS version installed
    Affected if Version matches < 22.4; = 22.4; = 23.2; = 23.4; = 24.2; = 24.4; = 25.2 for Junos OS, or < 23.2; = 23.2; = 23.4; = 24.2; = 24.4; = 25.2 for Junos OS Evolved
  2. Verify local CLI user accounts exist
    Run 'show system login' or review /var/etc/passwd to enumerate local user accounts with CLI access
    Affected if Local authenticated users exist on the system regardless of privilege level
  3. Review mgd logs for unauthorized show mgd command usage
    Run 'show mgd' command with various arguments (e.g., 'show mgd internal', 'show mgd schema') as a low-privilege user to test if sensitive information is accessible without proper authorization
    Affected if Low-privilege users can execute 'show mgd' commands with arguments that expose restricted sensitive information
  4. Check system logs for show mgd command history
    Examine system logs (e.g., /var/log/messages, audit logs) for 'show mgd' command entries from low-privilege users
    Affected if Logs show 'show mgd' command executions by users without elevated privileges

A user is affected if they are running a Junos OS or Junos OS Evolved version listed in the affected ranges AND have local authenticated CLI users present on the system.

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 22.4 / 23.2 or later
Fixed in 22.423.2
Interim mitigation

Apply the vendor-provided Junos OS patches by upgrading to the fixed versions specified in the advisory. Until then, limit local CLI access and monitor for unauthorized 'show mgd' command usage.

Recommended fix High confidence

Junos OS: 22.4R3-S8 or later, 23.2R2-S6 or later, 23.4R2-S6 or later, 24.2R2-S4 or later; Junos OS Evolved: 23.2R2-S6-EVO or later, 23.4R2-S6-EVO or later, 24.2R2-S4-EVO or later

  1. 1. Identify the current Junos OS or Junos OS Evolved version running on the device using 'show version'
  2. 2. Based on the current version branch, plan upgrade to the minimum fixed release: For 22.4 branch upgrade to 22.4R3-S8 or later; For 23.2 branch upgrade to 23.2R2-S6 or later; For 23.4 branch upgrade to 23.4R2-S6 or later; For 24.2 branch upgrade to 24.2R2-S4 or later
  3. 3. Review Juniper KB article kb.juniper.net for any specific upgrade procedures and prerequisites
  4. 4. Before upgrading in production, test the upgrade in a lab environment to verify compatibility
  5. 5. Perform a configuration backup using 'request system configuration rescue save'
  6. 6. Upgrade the device using 'request system software add <package>' with the appropriate fixed version
  7. 7. After upgrade, verify the fix by confirming the new version is running: 'show version'
  8. 8. Verify the vulnerability is remediated by confirming low-privilege users can no longer access sensitive information via 'show mgd' command
Caveat Standard Junos upgrade risks apply - ensure backups and test in lab first; some version jumps may require intermediate upgrades per Juniper migration guidelines

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

Fix this in Junos 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 the upgrade done

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-33776 — 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-33776 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