# CVE-2026-123765: Apache Sling XSS: xssAPI.getStyleToken() accepts markup in unquoted urls.

> Attackers can inject markup into unquoted URLs that Apache Sling XSS accepts, enabling cross-site scripting in applications using it.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Harmful if only installed:** No
- **Needs a specific call:** Yes (`xssAPI.getStyleToken()`)
- **Fix available:** No
- **Published:** 12 Nov 2026
- **Updated:** 12 Nov 2026
- **Also known as:** GHSA-rc4h-46w7-hp9c

## What is CVE-2026-123765?

CVE-2026-123765 is a cross-site scripting vulnerability in Apache Sling XSS, published on 12 Nov 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Improper neutralization of input during web page generation ('cross-site scripting') vulnerability in Apache Sling XSS. xssAPI.getStyleToken() accepts markup in unquoted urls.

This issue affects Apache Sling XSS: before 2.4.14.

Users are recommended to upgrade to version 2.4.14, which fixes the issue.

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

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

An affected version is only exploitable if your software calls xssAPI.getStyleToken(). Many projects that include it are not exposed.


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

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

## Is CVE-2026-123765 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-123765 is a cross-site scripting vulnerability in Apache Sling XSS, published on 12 Nov 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-123765 in the wild and no public exploit code.
Exposure: An affected version is only exploitable if your software calls xssAPI.getStyleToken(). Many projects that include it are not exposed.

Affected product: Apache Sling XSS. 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.
   If an affected version is present, also search the code for calls to xssAPI.getStyleToken() and report whether any exist.
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-123765/ (Markdown: https://insights.sbomify.com/CVE-2026-123765/index.md)
```

## Sources

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

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