# Anubis: Policy bypass via client controlled X-Original-URI header

Advisory record · `GHSA-6wcg-mqvh-fcvg`

- **Identifiers:** `GHSA-6wcg-mqvh-fcvg` · `CVE-2026-62314` · `GO-2026-6639`
- **State:** Confirmed
- **Severity:** CVSS 5.8 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-284](https://cwe.mitre.org/data/definitions/284.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 2 Oct 2026
- **Updated:** 7 Oct 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 2 Oct 2026, 18:22 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/TecharoHQ/anubis` (Go): affected `>=1.22.0, <1.26.0`; fixed in `1.26.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Anubis versions 1.22.0 through 1.25.0 can be bypassed by any HTTP client that adds a single X-Original-URI header, with no challenge needed. The default configuration is affected, and in reverse proxy mode the header reaches the policy check unchanged, letting a request pass straight to the upstream site. Upgrade to Anubis 1.26.0, which fixes the issue.

Written 1 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.8 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0034, the 27th percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:12 UTC: First seen by agentprime
- 31 Oct 2026, 14:12 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-6wcg-mqvh-fcvg)

## Sources

- [GitHub Advisory Database: GHSA-6wcg-mqvh-fcvg](https://github.com/advisories/GHSA-6wcg-mqvh-fcvg)
- [OSV: GHSA-6wcg-mqvh-fcvg](https://osv.dev/vulnerability/GHSA-6wcg-mqvh-fcvg)
- <https://github.com/TecharoHQ/anubis/security/advisories/GHSA-6wcg-mqvh-fcvg>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-62314>
- <https://github.com/TecharoHQ/anubis/pull/1630>
- <https://github.com/TecharoHQ/anubis/commit/276b537776b281b1c4e01421435bc03ade3d8fc4>
- <https://github.com/TecharoHQ/anubis>
- <https://github.com/TecharoHQ/anubis/releases/tag/v1.26.0-pre1>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-6wcg-mqvh-fcvg>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-6wcg-mqvh-fcvg/>. Everything for agents: <https://agentprime.io/llms.txt>.
