Skip to main content
VulnerabilityPublished

CVE-2025-59961: Juniper Networks Junos OS · Incorrect Permissions

Affects Juniper Networks Junos OSSource CVE Database V5

0

Not known to be exploited · CVSS 5.5 Medium · fixed in 25.2R1-S1 : update Juniper Networks Junos OS when convenient.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 25.2R1-S1, 24.4R2, 24.2R2-S2 +11
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
Juniper NetworksJunos OSAffected
  • <21.2R3-S10
  • >=21.4 <21.4R3-S12
  • >=22.4 <22.4R3-S8
  • >=23.2 <23.2R2-S5
  • >=23.4 <23.4R2-S6
  • >=24.2 <24.2R2-S2
  • >=24.4 <24.4R2
  • =22.2
  • =25.2
Fixed in
  • 25.2R1-S1
  • 24.4R2
  • 24.2R2-S2
  • 23.4R2-S6
  • 23.2R2-S5
  • 22.4R3-S8
  • 21.4R3-S12
  • 21.2R3-S10
Juniper NetworksJunos OS EvolvedAffected
  • <22.4R3-S8-EVO
  • >=23.2 <23.2R2-S5-EVO
  • >=23.4 <23.4R2-S6-EVO
  • >=24.2 <24.2R2-S2-EVO
  • >=24.4 <24.4R2-EVO
  • =25.2
Fixed in
  • 25.2R1-S1-EVO
  • 24.4R2-EVO
  • 24.2R2-S2-EVO
  • 23.4R2-S6-EVO
  • 23.2R2-S5-EVO
  • 22.4R3-S8-EVO

AI-suggested

European organizations should immediately identify all Juniper devices running affected versions of Junos OS and Junos OS Evolved, focusing on those providing DHCP server or relay services. Applying the vendor-provided patches for the affected versions is the primary mitigation step. In environments where immediate patching is not feasible, organizations should restrict local user access on these devices to trusted administrators only, minimizing the risk of exploitation by low-privileged users. Network segmentation and strict access controls should be enforced to limit who can log into network devices locally. Monitoring and alerting for unusual activity related to the jdhcpd process or Unix socket access can help detect exploitation attempts. Additionally, organizations should review and harden device configurations to ensure minimal local user accounts and enforce the principle of least privilege. Regular audits of device permissions and access logs will help identify potential misuse. Finally, maintaining an up-to-date asset inventory and vulnerability management program will ensure timely identification and remediation of such vulnerabilities.

Description

CVE-2025-59961 is a medium-severity vulnerability in Juniper Networks Junos OS and Junos OS Evolved affecting the DHCP daemon (jdhcpd). It allows a local, low-privileged user to write to the Unix socket managing the DHCP service, enabling administrative control over the DHCP server or relay. This flaw arises from incorrect permission assignments on a critical resource, permitting unauthorized command execution without user interaction. The vulnerability impacts multiple Junos OS versions prior to various patch releases starting from 21.2R3-S10 and corresponding Junos OS Evolved versions. Exploitation requires local access but no elevated privileges or user interaction. Although no known exploits are reported in the wild, the ability to control DHCP services can disrupt network operations and potentially facilitate further attacks. European organizations using affected Juniper devices should prioritize patching to mitigate risks.

References

Community reviews

Loading reviews…