# CVE-2026-95813: e621ng before 26.09.16 Open Redirect via URL Parameters

> Attackers can redirect users to malicious sites via manipulated URL parameters in pagination and navigation links, potentially facilitating phishing attacks.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N`)
- **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
- **Fix available:** No
- **Published:** 22 Sep 2026
- **Updated:** 26 Sep 2026
- **Also known as:** GHSA-7r53-6357-gf8f

## What is CVE-2026-95813?

CVE-2026-95813 is a medium-severity vulnerability in e621ng, published on 22 Sep 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

e621ng versions before 26.09.16 pass untrusted request parameters directly to Rails url_for in PaginatorComponent and controller navigation links, allowing attackers to redirect pagination and navigation controls to attacker-controlled origins. Attackers can supply host, protocol, and port query parameters that are interpreted as URL generation options, causing pagination links to point to malicious domains while the initial page loads from the legitimate site.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

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


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

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

## Is CVE-2026-95813 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-95813 is a medium-severity vulnerability in e621ng, published on 22 Sep 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-95813 in the wild and no public exploit code.

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

## Sources

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

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