# CVE-2026-24824: A XSS in yacy/yacy_search_server

> Cross-site scripting vulnerability in YaCy search server allows attackers to inject malicious scripts into web pages viewed by other users.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N/AU:Y/R:U/V:D/RE:M/U:Amber`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Jan 2026
- **Updated:** 27 Jan 2026
- **Also known as:** GHSA-49v6-p72m-p687

## What is CVE-2026-24824?

CVE-2026-24824 is a medium-severity cross-site scripting vulnerability in yacy_search_server, published on 27 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in yacy yacy_search_server (source/net/yacy/http/servlets modules). This vulnerability is associated with program files YaCyDefaultServlet.Java.

This issue affects yacy_search_server.

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

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


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

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

## Is CVE-2026-24824 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-24824 is a medium-severity cross-site scripting vulnerability in yacy_search_server, published on 27 Jan 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-24824 in the wild and no public exploit code.

Affected product: yacy_search_server. 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-24824/ (Markdown: https://insights.sbomify.com/CVE-2026-24824/index.md)
```

## Sources

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

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