Quick answers
- Is CVE-2026-15527 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-15527 being exploited in the wild.
- How severe is CVE-2026-15527?
- Medium severity, with a CVSS score of 5.3, published 13 July 2026.
- Which products and versions are affected?
- Better-Auth Better-Icons up to 1.0.5.
- Is there a fix for CVE-2026-15527?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-15527 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-15527?
- Check whether you run Better-Auth Better-Icons at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability consists of two primary issues within the 'scan_project_icons' and 'sync_icon' tools of the better-icons MCP server. First, the 'icons_file' argument lacks path validation, canonicalization, or project-root confinement, enabling path traversal (CWE-22) and arbitrary file writes (CWE-73). Second, the 'component_name' argument is inserted directly into generated JavaScript/TypeScript/Vue/Svelte templates without identifier validation, allowing for top-level source code injection (CWE-94). An attacker can exploit these to modify sensitive files or achieve code execution when the victim project is subsequently built or executed. The vulnerability is reachable via any MCP client or prompt-injected agent. As of the advisory date, no official patch has been released.
Affected products
- better-auth better-icons up to 1.0.5
Timeline
- 2026-07-13: advisory: NVD publication date
- 2026-07-13: disclosed: Public disclosure of the exploit and issue report