CVE-2026-57026

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-10. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

An Improper Validation of Syntactic Correctness of Input vulnerability in the SIP plugin of Juniper Networks Junos OS on MX Series with SPC3 and SRX Series allows an unauthenticated, network-based attacker to cause a Denial-of-Service (DoS).If the SIP ALG is enabled on an affected device, the processing of a malformed SIP invite packet will cause a flow processing daemon (flowd) crash and restart. This leads to a complete service outage until the system has automatically recovered.

This issue affects Junos OS on MX Series with SPC3 and SRX Series:

* all versions before 23.2R2-S7, * 23.4 versions before 23.4R2-S8, * 24.2 versions before 24.2R2-S5, * 24.4 versions before 24.4R2-S4, * 25.2 versions before 25.2R2, * 25.4 versions before 25.4R1-S2.

CVSS v3
7.5
EG Score
7.5(high)
EPSS
37.4%
KEV
Not listed

Published

July 9, 2026

Last Modified

July 14, 2026

Advisory Details (1)

Auto-updated Jul 9, 2026
No patch confirmed yet.
generic

CEC Juniper Community

https://supportportal.juniper.net/JSA110086

Vendor Advisories for CVE-2026-57026(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 35× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:25 UTCEPSS rescore
  3. 2026-07-20 17:08 UTCEPSS rescore
  4. 2026-07-19 14:31 UTCEPSS rescore
  5. 2026-07-19 14:31 UTCEPSS rescore
  6. 2026-07-19 02:29 UTCEPSS rescore
  7. 2026-07-18 10:04 UTCEPSS rescore
  8. 2026-07-17 06:28 UTCGHSA enrichment
  9. 2026-07-16 18:42 UTCGHSA enrichment
  10. 2026-07-16 17:03 UTCEPSS rescore
  11. 2026-07-16 06:56 UTCGHSA enrichment
  12. 2026-07-15 19:10 UTCGHSA enrichment
  13. 2026-07-15 16:57 UTCEPSS rescore
  14. 2026-07-15 16:57 UTCEPSS rescore
  15. 2026-07-15 07:23 UTCGHSA enrichment
  16. 2026-07-15 02:00 UTCEPSS rescore
  17. 2026-07-15 02:00 UTCEPSS rescore
  18. 2026-07-14 19:38 UTCGHSA enrichment
  19. 2026-07-14 07:46 UTCGHSA enrichment
  20. 2026-07-13 22:31 UTCEPSS rescore
  21. 2026-07-13 19:51 UTCGHSA enrichment
  22. 2026-07-13 08:05 UTCGHSA enrichment
  23. 2026-07-13 06:13 UTCEPSS rescore
  24. 2026-07-13 06:13 UTCEPSS rescore
  25. 2026-07-12 20:18 UTCGHSA enrichment
Show 10 more
  1. 2026-07-12 08:32 UTCGHSA enrichment
  2. 2026-07-12 05:46 UTCEPSS rescore
  3. 2026-07-11 20:46 UTCGHSA enrichment
  4. 2026-07-11 09:00 UTCGHSA enrichment
  5. 2026-07-11 08:27 UTCEPSS rescore
  6. 2026-07-11 08:27 UTCEPSS rescore
  7. 2026-07-10 21:14 UTCGHSA enrichment
  8. 2026-07-10 09:28 UTCGHSA enrichment
  9. 2026-07-09 21:42 UTCEG score recompute
  10. 2026-07-09 21:40 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-57026?
CVE-2026-57026 is a high vulnerability published on July 9, 2026. An Improper Validation of Syntactic Correctness of Input vulnerability in the SIP plugin of Juniper Networks Junos OS on MX Series with SPC3 and SRX Series allows an unauthenticated, network-based attacker to cause a Denial-of-Service (DoS).If the SIP ALG is enabled on an affected device, the…
When was CVE-2026-57026 disclosed?
CVE-2026-57026 was first published in the National Vulnerability Database on July 9, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-57026 actively exploited?
CVE-2026-57026 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 37.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-57026?
CVE-2026-57026 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-57026?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-57026, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-57026

Explore →

Is Your Infrastructure Affected by CVE-2026-57026?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs