Medium

CVE-2026-33779 — Junos OS: SRX Series: Insufficient certificate verification for device to SD cloud communication

An Improper Following of a Certificate's Chain of Trust vulnerability in J-Web of Juniper Networks Junos OS on SRX Series allows a PITM to intercept the communication of the device and get access to confidential information and potentially modify it. When an SRX device is provisioned to connect to Security Director (SD) cloud, it doesn't perform sufficient verification of the received server certificate. This allows a PITM to intercept the communication between the SRX and SD cloud and access credentials and other sensitive information. This issue affects Junos OS: * all versions before 22.4R3-S9, * 23.2 versions before 23.2R2-S6, * 23.4 versions before 23.4R2-S7, * 24.2 versions before 24.2R2-S3, * 24.4 versions before 24.4R2-S2, * 25.2 versions before 25.2R1-S2, 25.2R2.

Published Apr 9, 2026 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: juniper

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.2% (30-day exploitation probability)+1
Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.18%

ahead of 7% of scored CVEs · Oct 14, 2026

Affects

Juniper Networks

Junos and 1 more

CVSS base

6.5

Medium · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

None

none · proof-of-concept · active

Automatable

can an attacker script the kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Juniper Networks Junos, Juniper Networks Junos OS).
The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Juniper Networks	Junos	version 24.2-r1-s2version 23.4-r1version 23.4-r1-s1version 23.4-r1-s2version 23.4-r2version 23.4-r2-s1version 23.4-r2-s2version 23.4-r2-s3 and 47 more version 23.4-r2-s4version 23.4-r2-s5version 23.4-r2-s6version 24.2version 24.2-r1version 24.2-r1-s1version 22.4version 24.2-r2version 24.2-r2-s1version 24.2-r2-s2version 24.4version 24.4-r1version 24.4-r1-s2version 24.4-r1-s3version 24.4-r2version 24.4-r2-s1version 25.2version 25.2-r1version 25.2-r1-s1version 25.2-r2version 23.2-r2-s5< 22.4version 22.4-r1version 22.4-r1-s1version 22.4-r1-s2version 22.4-r2version 22.4-r2-s1version 22.4-r2-s2version 22.4-r3version 22.4-r3-s1version 22.4-r3-s2version 22.4-r3-s3version 22.4-r3-s4version 22.4-r3-s5version 22.4-r3-s7version 23.4version 23.2-r2-s4version 23.2-r2-s3version 23.2-r2-s2version 23.2-r2-s1version 23.2-r2version 23.2-r1-s2version 23.2-r1-s1version 23.2-r1version 23.2version 22.4-r3-s8version 22.4-r3-s6	Vulnerable	NIST National Vulnerability Database
Juniper Networks	Junos OS	< 22.4R3-S9≥ 23.2 and < 23.2R2-S6≥ 23.4 and < 23.4R2-S7≥ 24.2 and < 24.2R2-S3≥ 24.4 and < 24.4R2-S2≥ 25.2 and < 25.2R1-S2, 25.2R2	Vulnerable	CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Network

Attack complexity

High

Privileges required

None

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

Low

Availability

None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
8.3	CVSS 4.0	High	—	—	sirt@juniper.net via NIST National Vulnerability Database
8.3	CVSS 4.0	High	—	—	juniper via CVE Program (cve.org) e CISA ADP
6.5	CVSS 3.1	Medium	2.2	4.2	sirt@juniper.net via NIST National Vulnerability Database
6.5	CVSS 3.1	Medium	—	—	juniper via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N (score shown at the top: sirt@juniper.net)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-296

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.18%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).

web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

2026
Affected products added · juniper networks/junos os
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 13, 2026
CVSS changed · 6.5
Oct 13, 2026 · NIST National Vulnerability Database
Source status changed · → Analyzed
Oct 13, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 13, 2026 · NIST National Vulnerability Database
CVE published
Apr 9, 2026 · juniper

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

1 on the record

kb.juniper.net/JSA107823
Vendor Advisory, vendor-advisory, NIST National Vulnerability Database

Elsewhere on this site

Juniper Networks
every CVE for this vendor

CWE-296
other pages naming this weakness

Related CVEs (same products)

High CVE-2026-102077 Junos OS: MX Series with SPC3: In a source NAT scenario malformed packets will lead to resource leaks and eventually traffic stops 1d
Critical CVE-2026-101982 Junos OS and Junos OS Evolved: A EVPN peer causes an rpd crash or root-level compromise when EVPN-VPWS is used 1d
Critical CVE-2026-101983 Junos OS and Junos OS Evolved: An attacker causes remote code execution when J-Web virtual-domain is configured 1d
Medium CVE-2026-101964 Junos OS and Junos OS Evolved: An attacker can cause an rpd crash via a crafted LDP message 1d
Medium CVE-2026-101975 Junos OS and Junos OS Evolved: Improper OSPF LSA validation causes an rpd crash when prefix-SID best-route installation is used 1d
Medium CVE-2026-101972 Junos OS and Junos OS Evolved: Malformed OSPF packets causes routing disruption when OSPF is enabled 1d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No fixed version, patch or mitigation documented.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-33779 is "Junos OS: SRX Series: Insufficient certificate verification for device to SD cloud communication", rated Medium. It affects Junos (Juniper Networks); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 6.5 describes technical severity. EPSS 0.18% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.