dbcve.org
JunosOperating system · Juniper

CVE-2026-33786

MEDIUM · 5.5 CVSS v3.1 Published 2026-04-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
An Improper Check for Unusual or Exceptional Conditions vulnerability in the chassis control daemon (chassisd) of Juniper Networks Junos OS on SRX1600, SRX2300 and SRX4300 allows a local attacker with low privileges to cause a complete Denial of Service (DoS). When a specific 'show chassis' CLI command is executed, chassisd crashes and restarts which causes a momentary impact to all traffic until all modules are online again. This issue affects Junos OS on SRX1600, SRX2300 and SRX4300: * 24.4 versions before 24.4R1-S3, 24.4R2. This issue does not affect Junos OS versions before 24.4R1.

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 local low-privileged attacker can trigger a denial of service in Juniper SRX1600, SRX2300, and SRX4300 devices by executing a specific 'show chassis' CLI command, which causes the chassisd (chassis control daemon) to crash and restart, disrupting all traffic until modules reinitialize.

MitigationApply Juniper software updates 24.4R1-S3 or later (or 24.4R2) to resolve the improper error handling in the chassis control daemon.

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

CVSS:3.1/AV:L/AC:L/PR:L/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. Identify device model
    Run 'show chassis hardware' or check device model via 'show version' output to confirm it is an SRX1600, SRX2300, or SRX4300
    Affected if Device model is NOT SRX1600, SRX2300, or SRX4300 (not affected)
  2. Check Junos version
    Run 'show version' or 'show version detail' and locate the Junos version string
    Affected if Version is exactly 24.4 (vulnerable); versions earlier than 24.4 or later than 24.4 (including 24.4R1-S3 or 24.4R2 and later) are not affected by this specific CVE
  3. Verify chassis daemon status
    Run 'show system processes chassisd' or 'request system process daemon chassisd status' to check if the chassis control daemon is running
    Affected if Daemon is not running or has recently restarted (may indicate the vulnerability was triggered)
  4. Check for recent crash logs
    Run 'show log messages' and search for chassisd crash entries using 'grep -i chassisd' or 'show system core-dumps'
    Affected if Recent chassisd crash events are present in logs, indicating possible exploitation

Device is affected only if it is an SRX1600/SRX2300/SRX4300 running Junos version exactly 24.4 and the attacker has local CLI access to execute the malicious 'show chassis' command.

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

Apply Juniper software updates 24.4R1-S3 or later (or 24.4R2) to resolve the improper error handling in the chassis control daemon.

Recommended fix High confidence

24.4R1-S3 or 24.4R2

  1. Upgrade Junos OS on affected devices (SRX1600, SRX2300, SRX4300) to version 24.4R1-S3 or 24.4R2
  2. Verify the upgrade completed successfully by checking the Junos version with 'show version'
  3. Confirm the chassis control daemon is stable with 'show chassis' command - it should execute without crashing chassisd

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

Fix this in Junos Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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