CVE-2026-58476

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated
8.1EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.1Exploit: No code on recordExposed services: Not assessed

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

The CVE record's CNA (VulnCheck) lists Dan-in-CA SIP versions up to and including 5.2.16 as affected. No release containing a fix is confirmed on record.

Sustainable Irrigation Platform (SIP) through version 5.2.16 contains a cross-site request forgery vulnerability that allows remote attackers to perform state-changing administrative actions by luring a logged-in administrator into visiting a malicious page that issues HTTP GET requests without CSRF token validation or origin verification. Attackers can trigger actions such as disabling the passphrase, rebooting the device, deleting programs, or installing plugins, with the default configuration exposing these endpoints to unauthenticated users due to no required passphrase and a default credential of 'opendoor'.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
52
EG Risk 52/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity81% × 45%
The EG Score, 8.1 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.3%
EPSS %ILE
17th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 14, 2026

Last Modified

July 14, 2026

Advisory Details (2)

Auto-updated Jul 14, 2026
No fix on record yet.
Web page

Zero Science Lab — Information Security Research & Development Laboratory

https://www.zeroscience.mk/#/advisories/ZSL-2026-5995
Web page

Sustainable Irrigation Platform 5.2.16 CSRF via Administrative GET Requests | Advisories | VulnCheck

https://www.vulncheck.com/advisories/sustainable-irrigation-platform-csrf-via-administrative-get-requests

Vendor Advisories for CVE-2026-58476(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 / 40× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 228 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 128 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  3. 2026-10-12 15:53 UTCEG score recompute
  4. 2026-10-11 19:36 UTCEG score recompute
  5. 2026-10-11 16:52 UTCEG score recompute
  6. 2026-10-11 14:14 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  10. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  11. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  12. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  13. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  14. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  15. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  16. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  17. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  18. 2026-10-01 13:25 UTCEG score recompute
  19. 2026-10-01 13:25 UTCGHSA enrichmentGHSA-5j3h-8rxj-3v3m · GitHub severity HIGH · GitHub CVSS 8.1
  20. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  21. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  22. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  23. 2026-09-28 09:23 UTCEG score recompute
  24. 2026-09-28 09:23 UTCGHSA enrichmentGHSA-5j3h-8rxj-3v3m · GitHub severity HIGH · GitHub CVSS 8.1
  25. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.3% · 17th percentile
Show 75 more
  1. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  2. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  3. 2026-09-24 09:54 UTCEG score recompute
  4. 2026-09-24 09:54 UTCGHSA enrichmentGHSA-5j3h-8rxj-3v3m · GitHub severity HIGH · GitHub CVSS 8.1
  5. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  6. 2026-09-23 03:57 UTCEG score recompute
  7. 2026-09-23 03:57 UTCGHSA enrichmentGHSA-5j3h-8rxj-3v3m · GitHub severity HIGH · GitHub CVSS 8.1
  8. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  9. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  10. 2026-09-18 04:55 UTCEG score recompute
  11. 2026-09-18 04:55 UTCGHSA enrichmentGHSA-5j3h-8rxj-3v3m · GitHub severity HIGH · GitHub CVSS 8.1
  12. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  13. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  14. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  15. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  16. 2026-09-14 11:08 UTCGHSA enrichmentGHSA-5j3h-8rxj-3v3m · GitHub severity HIGH · GitHub CVSS 8.1
  17. 2026-09-13 23:28 UTCEG score recompute
  18. 2026-09-13 23:28 UTCGHSA enrichmentGHSA-5j3h-8rxj-3v3m · GitHub severity HIGH · GitHub CVSS 8.1
  19. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  20. 2026-09-13 07:55 UTCEG score recompute
  21. 2026-09-13 07:55 UTCGHSA enrichmentGHSA-5j3h-8rxj-3v3m · GitHub severity HIGH · GitHub CVSS 8.1
  22. 2026-09-12 13:27 UTCGHSA enrichmentGHSA-5j3h-8rxj-3v3m · GitHub severity HIGH · GitHub CVSS 8.1
  23. 2026-09-12 01:46 UTCEG score recompute
  24. 2026-09-12 01:46 UTCGHSA enrichmentGHSA-5j3h-8rxj-3v3m · GitHub severity HIGH · GitHub CVSS 8.1
  25. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  26. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  27. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  28. 2026-09-08 01:47 UTCEG score recompute
  29. 2026-09-08 01:47 UTCGHSA enrichmentGHSA-5j3h-8rxj-3v3m · GitHub severity HIGH · GitHub CVSS 8.1
  30. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  31. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  32. 2026-09-06 13:47 UTCGHSA enrichmentGHSA-5j3h-8rxj-3v3m · GitHub severity HIGH · GitHub CVSS 8.1
  33. 2026-09-05 21:18 UTCEG score recompute
  34. 2026-09-05 21:18 UTCGHSA enrichmentGHSA-5j3h-8rxj-3v3m · GitHub severity HIGH · GitHub CVSS 8.1
  35. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  36. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  37. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  38. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  39. 2026-08-31 05:44 UTCEG score recompute
  40. 2026-08-31 05:44 UTCGHSA enrichmentGHSA-5j3h-8rxj-3v3m · GitHub severity HIGH · GitHub CVSS 8.1
  41. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  42. 2026-08-30 17:06 UTCGHSA enrichmentGHSA-5j3h-8rxj-3v3m · GitHub severity HIGH · GitHub CVSS 8.1
  43. 2026-08-30 05:25 UTCEG score recompute
  44. 2026-08-30 05:25 UTCGHSA enrichmentGHSA-5j3h-8rxj-3v3m · GitHub severity HIGH · GitHub CVSS 8.1
  45. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  46. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  47. 2026-08-28 02:28 UTCEG score recompute
  48. 2026-08-28 02:28 UTCGHSA enrichmentGHSA-5j3h-8rxj-3v3m · GitHub severity HIGH · GitHub CVSS 8.1
  49. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  50. 2026-08-27 13:53 UTCGHSA enrichmentGHSA-5j3h-8rxj-3v3m · GitHub severity HIGH · GitHub CVSS 8.1
  51. 2026-08-27 01:28 UTCEG score recompute
  52. 2026-08-27 01:28 UTCGHSA enrichmentGHSA-5j3h-8rxj-3v3m · GitHub severity HIGH · GitHub CVSS 8.1
  53. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  54. 2026-08-26 13:48 UTCGHSA enrichmentGHSA-5j3h-8rxj-3v3m · GitHub severity HIGH · GitHub CVSS 8.1
  55. 2026-08-26 01:50 UTCEG score recompute
  56. 2026-08-26 01:50 UTCGHSA enrichmentGHSA-5j3h-8rxj-3v3m · GitHub severity HIGH · GitHub CVSS 8.1
  57. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  58. 2026-08-25 09:33 UTCGHSA enrichmentGHSA-5j3h-8rxj-3v3m · GitHub severity HIGH · GitHub CVSS 8.1
  59. 2026-08-24 21:43 UTCEG score recompute
  60. 2026-08-24 21:43 UTCGHSA enrichmentGHSA-5j3h-8rxj-3v3m · GitHub severity HIGH · GitHub CVSS 8.1
  61. 2026-08-24 09:58 UTCEG score recompute
  62. 2026-08-24 09:58 UTCGHSA enrichmentGHSA-5j3h-8rxj-3v3m · GitHub severity HIGH · GitHub CVSS 8.1
  63. 2026-08-23 22:17 UTCGHSA enrichmentGHSA-5j3h-8rxj-3v3m · GitHub severity HIGH · GitHub CVSS 8.1
  64. 2026-08-23 10:30 UTCEG score recompute
  65. 2026-08-23 10:30 UTCGHSA enrichmentGHSA-5j3h-8rxj-3v3m · GitHub severity HIGH · GitHub CVSS 8.1
  66. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  67. 2026-08-22 22:50 UTCGHSA enrichmentGHSA-5j3h-8rxj-3v3m · GitHub severity HIGH · GitHub CVSS 8.1
  68. 2026-08-22 11:10 UTCEG score recompute
  69. 2026-08-22 11:10 UTCGHSA enrichmentGHSA-5j3h-8rxj-3v3m · GitHub severity HIGH · GitHub CVSS 8.1
  70. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  71. 2026-08-21 23:29 UTCGHSA enrichmentGHSA-5j3h-8rxj-3v3m · GitHub severity HIGH · GitHub CVSS 8.1
  72. 2026-08-21 11:48 UTCGHSA enrichmentGHSA-5j3h-8rxj-3v3m · GitHub severity HIGH · GitHub CVSS 8.1
  73. 2026-08-20 23:57 UTCEG score recompute
  74. 2026-08-20 23:57 UTCGHSA enrichmentGHSA-5j3h-8rxj-3v3m · GitHub severity HIGH · GitHub CVSS 8.1
  75. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.2% · 13th percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-58476?
CVE-2026-58476 is a high-severity vulnerability; its CVE record was published on July 14, 2026. Sustainable Irrigation Platform (SIP) through version 5.2.16 contains a cross-site request forgery vulnerability that allows remote attackers to perform state-changing administrative actions by luring a logged-in administrator into visiting a malicious page that issues HTTP GET requests without…
When was CVE-2026-58476 made public?
CVE-2026-58476 was made public on July 14, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on July 14, 2026. EchelonGraph's copy of the record carries a last-modified date of July 14, 2026; the record at its source may have been updated since.
Is CVE-2026-58476 actively exploited?
CVE-2026-58476 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (17th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-58476?
CVE-2026-58476 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-58476?
No fix for CVE-2026-58476 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (VulnCheck) lists Dan-in-CA SIP versions up to and including 5.2.16 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-58476 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-58476?

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

Book a Demo →Browse All CVEs