# CVE-2026-94243: Apache Sling Security Bundle: RefererFilter accepts weaker-than-origin evidence

> Attackers can bypass the ReferrerFilter by providing weaker origin evidence, allowing unauthorized access to protected resources.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** GHSA-h9q6-hwx8-gw7h

## What is CVE-2026-94243?

CVE-2026-94243 is a high-severity vulnerability in Apache Sling Security Bundle, published on 23 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in Apache Sling Security Bundle: the ReferrerFilter accepts weaker-than-orgin evidence.

This issue affects Apache Sling Security Bundle: before 1.3.2.

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

Weakness: CWE-346 (Origin Validation Error)

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

It affects 1 product.


Products: Apache Sling Security.

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

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

## Is CVE-2026-94243 being exploited?

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

## Other vulnerabilities in Apache Sling Security Bundle

- [CVE-2026-94251](https://insights.sbomify.com/CVE-2026-94251/): Apache Sling Security Bundle: ContentDispositionFilter mediates only one address/API shape of a resource (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-94243 is a high-severity vulnerability in Apache Sling Security Bundle, published on 23 Sep 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-94243 in the wild and no public exploit code.

Affected product: Apache Sling Security Bundle. 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-94243/ (Markdown: https://insights.sbomify.com/CVE-2026-94243/index.md)
```

## Sources

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

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