# CVE-2026-35508: Cross-site scripting in Shynet

> Cross-site scripting in Shynet allows attackers to inject malicious scripts via URL display and iconify filters.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Apr 2026
- **Updated:** 3 Apr 2026
- **Also known as:** GHSA-92xp-7pvg-5vqp

## What is CVE-2026-35508?

CVE-2026-35508 is a medium-severity cross-site scripting vulnerability in milesmcc Shynet, published on 3 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Shynet before 0.14.0 allows XSS in urldisplay and iconify template filters,

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-35508?

It affects 1 product.


Products: Shynet Shynet.

## How do I fix CVE-2026-35508?

No fix has been published for CVE-2026-35508 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-35508 being exploited?

There is no known exploitation of CVE-2026-35508 in the wild and no public exploit code.

## Other vulnerabilities in milesmcc Shynet

- [CVE-2026-35507](https://insights.sbomify.com/CVE-2026-35507/): Open redirect in Shynet (medium 6.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-35508 and fix it if it is affected.

What it is: CVE-2026-35508 is a medium-severity cross-site scripting vulnerability in milesmcc Shynet, published on 3 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-35508 in the wild and no public exploit code.

Affected product: milesmcc Shynet. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-35508/ (Markdown: https://insights.sbomify.com/CVE-2026-35508/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-35508
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-35508
- OSV: https://osv.dev/vulnerability/CVE-2026-35508

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-35508/
Summaries are generated and may contain mistakes; the official description above is the record.