Junos OS: Mismatched Memory Management Routines
CVE-2026-102025 is a high-severity mismatched memory management routines vulnerability in Junos OS from Juniper Networks, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 23.2R2-S7.7, 23.4R2-S8.13, 24.2R2-S5.5 as the first without the flaw, so updating Junos OS to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.46% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Junos OS to 23.2R2-S7.7 or 23.4R2-S8.13 or 24.2R2-S5.5 or 24.4R2-S5, whichever matches your release line, or a later version.
- Update Junos OS Evolved to 23.2R2-S7.7-EVO or 23.4R2-S8.11-EVO or 24.2R2-S5.6-EVO or 24.4R2-S5-EVO, whichever matches your release line, or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Juniper Networks | Junos OS | before 23.2R2-S7.7; 23.4 up to, but not including, 23.4R2-S8.13; 24.2 up to, but not including, 24.2R2-S5.5; 24.4 up to, but not including, 24.4R2-S5; 25.2 up to, but not including, 25.2R2-S2; 25.4 up to, but not including, 25.4R1-S3; 26.2 up to, but not including, 26.2R1-S2 | 23.2R2-S7.7, 23.4R2-S8.13, 24.2R2-S5.5, 24.4R2-S5, 25.2R2-S2, 25.4R1-S3 |
| Juniper Networks | Junos OS Evolved | before 23.2R2-S7.7-EVO; 23.4 up to, but not including, 23.4R2-S8.11-EVO; 24.2 up to, but not including, 24.2R2-S5.6-EVO; 24.4 up to, but not including, 24.4R2-S5-EVO; 25.2 up to, but not including, 25.2R2-S2-EVO; 25.4 up to, but not including, 25.4R1-S3-EVO; 26.2 up to, but not including, 26.2R1-S2-EVO; 23.4X100; and 2 more ranges | 23.2R2-S7.7-EVO, 23.4R2-S8.11-EVO, 24.2R2-S5.6-EVO, 24.4R2-S5-EVO, 25.2R2-S2-EVO, 25.4R1-S3-EVO |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by CNA (juniper.net).
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 8.7 | High | CNA (juniper.net) |
| CVSS 3.1 | 7.5 | High | CNA (juniper.net) |
Official description
A Mismatched Memory Management Routines vulnerability in the routing protocol daemon (rpd) process of Juniper Networks Junos OS and Junos OS Evolved allows an authenticated network-based attacker to cause a denial of service via a BGP route update when extended next-hop tunneling and SRv6 service processing are used.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Mismatched Memory Management Routines
The product attempts to return a memory resource to the system, but it calls a release function that is not compatible with the function that was originally used to allocate that resource.
How developers prevent this class of flaw
- Only call matching memory management functions. Do not mix and match routines. For example, when you allocate a buffer with malloc(), dispose of the original pointer with free().
- Choose a language or tool that provides automatic memory management, or makes manual memory management less error-prone. For example, glibc in Linux provides protection against free of invalid pointers. When using Xcode to target OS X or iOS, enable automatic reference counting (ARC). To help correctly and consistently manage memory when programming in C++, consider using a smart pointer class such as std
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, glibc in Linux provides protection against free of invalid pointers.
More Mismatched Memory Management Routines vulnerabilities (CWE-762)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Other references
Other vulnerabilities in Junos OS
- 7.5 High severity
- 9.8 Critical severity
- 9.8 Critical severity
- 8.8 High severity
- 8.8 High severity
- 7.5 High severity
Recent Mismatched Memory Management Routines vulnerabilities
- 7.5 High severity
- 7.5 High severity
- 7.4 High severity
Spotted an error? Tell us.