CVE-2026-15319

HIGHPre-NVD 7.37.3
EchelonGraph scoreMEDIUM confidence

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

Score 7.3 from GitHub Security Advisory published 2026-07-10. A secondary CVSS source baseline 7.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated
7.3EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (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.5%CVSS: 7.3Exploit: No code on recordExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

A security vulnerability has been detected in Sipeed PicoClaw up to 0.2.9. This affects the function IPAllowlist of the file web/backend/middleware/access_control.go of the component Launcher. Such manipulation leads to improper access controls. The attack may be performed from remote. The exploit has been disclosed publicly and may be used. The name of the patch is 3126. A patch should be applied to remediate this issue.

CVSS v3
7.3
EG Score
7.3HIGHmedium confidence
EG Risk
64
EG Risk 64/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)
Severity73% × 45%
The EG Score, 7.3 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high until it ships, then apply the release.
EPSS PROB
0.5%
EPSS %ILE
44th
KEV
Not listed

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

An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high until it ships, then apply the release.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (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 10, 2026

Last Modified

July 10, 2026

Advisory Details (3)

Auto-updated Jul 10, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr.
GitHub pull request

fix(web): improve launcher allowlist bypass diagnostics

Fix merged in sipeed/picoclaw PR #3126 on 2026-06-15 — awaiting tagged release

https://github.com/sipeed/picoclaw/pull/3126
Web page

[Security] PicoClaw launcher `allowed_cidrs` can be bypassed through a same-host reverse proxy because access control trusts `RemoteAddr` · Issue #3069 · sipeed/picoclaw · GitHub

https://github.com/sipeed/picoclaw/issues/3069
Web page

GitHub - sipeed/picoclaw: Tiny, Fast, and Deployable anywhere — automate the mundane, unleash your creativity · GitHub

https://github.com/sipeed/picoclaw/

Vendor Advisories for CVE-2026-15319(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 34× 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 235 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 135 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-15319?
CVE-2026-15319 is a high-severity vulnerability; its CVE record was published on July 10, 2026. A security vulnerability has been detected in Sipeed PicoClaw up to 0.2.9. This affects the function IPAllowlist of the file web/backend/middleware/access_control.go of the component Launcher. Such manipulation leads to improper access controls. The attack may be performed from remote. The exploit…
When was the CVE record for CVE-2026-15319 published?
The CVE record for CVE-2026-15319 was published on July 10, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 10, 2026; the record at its source may have been updated since.
Is CVE-2026-15319 actively exploited?
CVE-2026-15319 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-15319?
CVE-2026-15319 has a CVSS base score of 7.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-15319?
An upstream fix for CVE-2026-15319 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-15319 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-15319?

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

Book a Demo →Browse All CVEs