Anubis: Policy bypass via client controlled X-Original-URI header
CVE-2026-62314GHSA-6wcg-mqvh-fcvg
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/TecharoHQ/anubis 1.26.0), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Go github.com/TecharoHQ/anubis
- Affected
- >= 1.22.0, < 1.26.0
- Fixed in
- 1.26.0
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GO-2026-6639 lists affected ranges: Go github.com/TecharoHQ/anubis >=1.22.0 <1.26.0 (fixed)
VerifiedObserved Structured OSV record; not marked as GitHub-reviewed.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-6wcg-mqvh-fcvg lists affected ranges: Go github.com/TecharoHQ/anubis >=1.22.0 <1.26.0 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-6wcg-mqvh-fcvg lists affected ranges: Go github.com/TecharoHQ/anubis >=1.22.0 <1.26.0
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 5.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N
- EPSS
- CVE-2026-62314: 0.34% estimated exploitation activity in the next 30 days; percentile 27.49 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Any HTTP client can bypass Anubis bot protection on the default configuration by adding a single request header. No challenge needs to be solved. Affected versions: v1.22.0 through v1.25.0 (introduced in commit d1d631a, PR #1015) The root cause is in lib/policy/checker.go, PathChecker.Check(): The header value comes directly from the client request. The middleware chain never strips it. In reverse proxy mode an attacker fully controls it. The default policy imports data/common/keep-internet-working.yaml, which contains path-only ALLOW rules with no other conditions: When X-Original-URI matches one of those regexes, the rule fires as ALLOW and the request is forwarded upstream without any challenge or JWT check. Proof of concept Normal request, gets challenged: Bypass, gets upstream content: The first command returns the Anubis challenge page title. The second returns the real site title directly, with no cookie set and no challenge issued. Verified live against anubis.techaro.lol.…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-6wcg-mqvh-fcvg
- Revision 2 · amended ·
Amended from osv record GO-2026-6639
- Revision 1 · created ·
Published from osv record GHSA-6wcg-mqvh-fcvg
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-62314 Advisory: Anubis: Policy bypass via client controlled X-Original-URI header IDs: CVE-2026-62314, GHSA-6wcg-mqvh-fcvg Record: https://patchnext.com/advisories/cve-2026-62314 (revision 3, source checked 26 Oct 2026, 15:29 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 5.8) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: github.com/TecharoHQ/anubis 1.26.0. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/TecharoHQ/anubis: affected >= 1.22.0, < 1.26.0; fixed in 1.26.0 ## Suggested inspection (read-only) - Go github.com/TecharoHQ/anubis: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on github.com/TecharoHQ/anubis. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GO-2026-6639 (OSV record GO-2026-6639 lists affected ranges: Go github.com/TecharoHQ/anubis >=1.22.0 <1.26.0 (fixed)) - Verified: https://osv.dev/vulnerability/GHSA-6wcg-mqvh-fcvg (OSV record GHSA-6wcg-mqvh-fcvg lists affected ranges: Go github.com/TecharoHQ/anubis >=1.22.0 <1.26.0 (fixed)) - Verified: https://github.com/advisories/GHSA-6wcg-mqvh-fcvg (GitHub-reviewed advisory GHSA-6wcg-mqvh-fcvg lists affected ranges: Go github.com/TecharoHQ/anubis >=1.22.0 <1.26.0) Commands are suggestions: review each one before running it.
Loading voting…