CVE-2026-15527

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated
5.3EG
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.2%CVSS: 5.3Exploit: 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 description, written by its CNA (VulDB), states the affected versions: "A vulnerability has been found in better-auth better-icons up to 1.0.5." No release containing a fix is confirmed on record.

A vulnerability has been found in better-auth better-icons up to 1.0.5. This vulnerability affects unknown code of the component scan_project_icons/sync_icon. Such manipulation of the argument icons_file leads to path traversal. An attack has to be approached locally. The exploit has been disclosed to the public and may be used. The project was informed of the problem early through an issue report but has not responded yet.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
40
EG Risk 40/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)
Severity53% × 45%
The EG Score, 5.3 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.2%
EPSS %ILE
6th
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 13, 2026

Last Modified

July 13, 2026

Advisory Details (2)

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

GitHub - better-auth/better-icons: Skill and MCP server for searching and retrieving icons · GitHub

https://github.com/better-auth/better-icons/
Web page

[Potential Vulnerability] better-icons sync_icon allows out-of-scope file writes and source-code injection · Issue #18 · better-auth/better-icons · GitHub

https://github.com/better-auth/better-icons/issues/18

Vendor Advisories for CVE-2026-15527(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 10× in last 7d / 33× 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 177 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 77 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.2% · 6th percentile
  2. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  3. 2026-10-12 16:31 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-10 19:59 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  8. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  9. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  10. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  11. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  12. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  13. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  14. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  15. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  16. 2026-10-01 14:47 UTCEG score recompute
  17. 2026-10-01 14:47 UTCGHSA enrichmentGHSA-2gq8-477v-cpgh · GitHub severity LOW · GitHub CVSS 5.3
  18. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  19. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  20. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  21. 2026-09-28 09:38 UTCEG score recompute
  22. 2026-09-28 09:38 UTCGHSA enrichmentGHSA-2gq8-477v-cpgh · GitHub severity LOW · GitHub CVSS 5.3
  23. 2026-09-27 13:47 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  24. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  25. 2026-09-24 10:16 UTCEG score recompute
Show 75 more
  1. 2026-09-24 10:16 UTCGHSA enrichmentGHSA-2gq8-477v-cpgh · GitHub severity LOW · GitHub CVSS 5.3
  2. 2026-09-23 05:36 UTCEG score recompute
  3. 2026-09-23 05:36 UTCGHSA enrichmentGHSA-2gq8-477v-cpgh · GitHub severity LOW · GitHub CVSS 5.3
  4. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  5. 2026-09-18 05:09 UTCEG score recompute
  6. 2026-09-18 05:09 UTCGHSA enrichmentGHSA-2gq8-477v-cpgh · GitHub severity LOW · GitHub CVSS 5.3
  7. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  8. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  9. 2026-09-14 06:47 UTCEG score recompute
  10. 2026-09-14 06:47 UTCGHSA enrichmentGHSA-2gq8-477v-cpgh · GitHub severity LOW · GitHub CVSS 5.3
  11. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  12. 2026-09-13 08:04 UTCEG score recompute
  13. 2026-09-13 08:04 UTCGHSA enrichmentGHSA-2gq8-477v-cpgh · GitHub severity LOW · GitHub CVSS 5.3
  14. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  15. 2026-09-12 01:58 UTCEG score recompute
  16. 2026-09-12 01:58 UTCGHSA enrichmentGHSA-2gq8-477v-cpgh · GitHub severity LOW · GitHub CVSS 5.3
  17. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  18. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  19. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  20. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  21. 2026-09-08 02:15 UTCEG score recompute
  22. 2026-09-08 02:14 UTCGHSA enrichmentGHSA-2gq8-477v-cpgh · GitHub severity LOW · GitHub CVSS 5.3
  23. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  24. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  25. 2026-09-05 21:31 UTCEG score recompute
  26. 2026-09-05 21:31 UTCGHSA enrichmentGHSA-2gq8-477v-cpgh · GitHub severity LOW · GitHub CVSS 5.3
  27. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  28. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  29. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  30. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  31. 2026-08-30 05:42 UTCEG score recompute
  32. 2026-08-30 05:42 UTCGHSA enrichmentGHSA-2gq8-477v-cpgh · GitHub severity LOW · GitHub CVSS 5.3
  33. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  34. 2026-08-28 02:37 UTCEG score recompute
  35. 2026-08-28 02:37 UTCGHSA enrichmentGHSA-2gq8-477v-cpgh · GitHub severity LOW · GitHub CVSS 5.3
  36. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  37. 2026-08-27 01:23 UTCEG score recompute
  38. 2026-08-27 01:23 UTCGHSA enrichmentGHSA-2gq8-477v-cpgh · GitHub severity LOW · GitHub CVSS 5.3
  39. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  40. 2026-08-26 02:40 UTCEG score recompute
  41. 2026-08-26 02:40 UTCGHSA enrichmentGHSA-2gq8-477v-cpgh · GitHub severity LOW · GitHub CVSS 5.3
  42. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  43. 2026-08-24 21:45 UTCEG score recompute
  44. 2026-08-24 21:45 UTCGHSA enrichmentGHSA-2gq8-477v-cpgh · GitHub severity LOW · GitHub CVSS 5.3
  45. 2026-08-23 23:04 UTCGHSA enrichmentGHSA-2gq8-477v-cpgh · GitHub severity LOW · GitHub CVSS 5.3
  46. 2026-08-23 00:22 UTCEG score recompute
  47. 2026-08-23 00:22 UTCGHSA enrichmentGHSA-2gq8-477v-cpgh · GitHub severity LOW · GitHub CVSS 5.3
  48. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  49. 2026-08-22 01:40 UTCEG score recompute
  50. 2026-08-22 01:40 UTCGHSA enrichmentGHSA-2gq8-477v-cpgh · GitHub severity LOW · GitHub CVSS 5.3
  51. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  52. 2026-08-21 02:58 UTCEG score recompute
  53. 2026-08-21 02:58 UTCGHSA enrichmentGHSA-2gq8-477v-cpgh · GitHub severity LOW · GitHub CVSS 5.3
  54. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  55. 2026-08-20 04:12 UTCEG score recompute
  56. 2026-08-20 04:12 UTCGHSA enrichmentGHSA-2gq8-477v-cpgh · GitHub severity LOW · GitHub CVSS 5.3
  57. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  58. 2026-08-19 05:27 UTCEG score recompute
  59. 2026-08-19 05:26 UTCGHSA enrichmentGHSA-2gq8-477v-cpgh · GitHub severity LOW · GitHub CVSS 5.3
  60. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  61. 2026-08-18 06:17 UTCEG score recompute
  62. 2026-08-18 06:17 UTCGHSA enrichmentGHSA-2gq8-477v-cpgh · GitHub severity LOW · GitHub CVSS 5.3
  63. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  64. 2026-08-17 07:34 UTCEG score recompute
  65. 2026-08-17 07:34 UTCGHSA enrichmentGHSA-2gq8-477v-cpgh · GitHub severity LOW · GitHub CVSS 5.3
  66. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  67. 2026-08-16 08:53 UTCEG score recompute
  68. 2026-08-16 08:53 UTCGHSA enrichmentGHSA-2gq8-477v-cpgh · GitHub severity LOW · GitHub CVSS 5.3
  69. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  70. 2026-08-15 10:12 UTCEG score recompute
  71. 2026-08-15 10:12 UTCGHSA enrichmentGHSA-2gq8-477v-cpgh · GitHub severity LOW · GitHub CVSS 5.3
  72. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  73. 2026-08-14 11:31 UTCEG score recompute
  74. 2026-08-14 11:31 UTCGHSA enrichmentGHSA-2gq8-477v-cpgh · GitHub severity LOW · GitHub CVSS 5.3
  75. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.1% · 3rd percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-15527?
CVE-2026-15527 is a medium-severity vulnerability; its CVE record was published on July 13, 2026. A vulnerability has been found in better-auth better-icons up to 1.0.5. This vulnerability affects unknown code of the component scanprojecticons/syncicon. Such manipulation of the argument iconsfile leads to path traversal. An attack has to be approached locally. The exploit has been disclosed to…
When was the CVE record for CVE-2026-15527 published?
The CVE record for CVE-2026-15527 was published on July 13, 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 13, 2026; the record at its source may have been updated since.
Is CVE-2026-15527 actively exploited?
CVE-2026-15527 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-15527?
CVE-2026-15527 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-15527?
No fix for CVE-2026-15527 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 description, written by its CNA (VulDB), states the affected versions: "A vulnerability has been found in better-auth better-icons up to 1.0.5." No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-15527 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-15527?

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

Book a Demo →Browse All CVEs