CVE-2026-62314: Anubis Policy Bypass Vulnerability

MODERATE
Advisory Identifier: GHSA-6wcg-mqvh-fcvg
CVSS 5.8
CWE-284
Published
Advisory Summary

CVE-2026-62314 is a MODERATE (CVSS 5.8) policy bypass vulnerability (CWE-284: Improper Access Control) affecting Anubis libraries in the Go ecosystem. The issue involves policy bypass via client controlled x-original-uri header. Remediation is available by upgrading affected packages to version 1.26.0.

CVE-2026-62314 at a Glance

CVE Identifier CVE-2026-62314
GHSA Identifier GHSA-6wcg-mqvh-fcvg
Severity MODERATE
CVSS v3.1 Base Score 5.8
CWE Classification CWE-284: Improper Access Control
Affected Product Anubis
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 5.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality Low (C:L)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2026-62314

To remediate this vulnerability, upgrade all affected Anubis dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/TecharoHQ/anubis fixed: 1.26.0
Upgrade github.com/TecharoHQ/anubis to 1.26.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/TecharoHQ/anubis

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-62314, inspect your project dependencies for Anubis:

inspect dependencies for github.com/TecharoHQ/anubis

Analyze the terminal output to locate any version of Anubis in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.26.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-284: Improper Access Control, where the product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. In Anubis, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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()`: ```go func (pc *PathChecker) Check(r *http.Request) (bool, error) { originalUrl := r.Header.Get("X-Original-URI") if originalUrl != "" { if pc.regexp.MatchString(originalUrl) { return true, nil } } if pc.regexp.MatchString(r.URL.Path) { return true, nil } return false, nil } ``` 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: ```yaml - name: well-known path_regex: ^/\.well-known/.*$ action: ALLOW ``` 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: ``` curl -s https://anubis.techaro.lol/ | grep -o "<title>.*</title>" ``` Bypass, gets upstream content: ``` curl -s -H "X-Original-URI: /.well-known/x" https://anubis.techaro.lol/ | grep -o "<title>.*</title>" ``` 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. # Suggested fix The fix should probably be to strip the header from incoming client requests in the middleware chain before policy evaluation. In `auth_request` mode the header is set by the proxy after Anubis processes the middleware, so stripping it at ingress does not break that deployment mode.

CVE-2026-62314 Affected Anubis Versions

1 component(s)
Fixed Versions:
1.26.0
Product / Package Ecosystem Affected Versions Fixed Version
github.com/TecharoHQ/anubis
Go
≥ 1.22.0
< 1.26.0
1.26.0

References

Frequently Asked Questions

What is CVE-2026-62314?
CVE-2026-62314 is a security vulnerability in Anubis involving Policy bypass via client controlled X-Original-URI header under CWE-284: Improper Access Control.
Which Anubis versions are affected?
Affected versions include releases prior to 1.26.0 across affected packages: github.com/TecharoHQ/anubis.
What version fixes CVE-2026-62314?
Upgrading to 1.26.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/TecharoHQ/anubis affected?
Yes, github.com/TecharoHQ/anubis is affected in releases prior to 1.26.0. Upgrade your dependency to 1.26.0 or later.
What is the CVSS score of CVE-2026-62314?
CVE-2026-62314 has a CVSS v3.1 base score of 5.8 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N.
What CWE is associated with CVE-2026-62314?
CVE-2026-62314 is classified under CWE-284: Improper Access Control (The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.).
How can I check Go dependencies for CVE-2026-62314?
Run the dependency tree command: 'inspect dependencies for github.com/TecharoHQ/anubis'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-6wcg-mqvh-fcvg",
  "modified" : "2026-10-02T18:22:08Z",
  "published" : "2026-10-02T18:22:08Z",
  "aliases" : [ "CVE-2026-62314" ],
  "summary" : "Anubis: Policy bypass via client controlled X-Original-URI header",
  "details" : "Any HTTP client can bypass Anubis bot protection on the default configuration by adding a single request header. No challenge needs to be solved.\nAffected versions: v1.22.0 through v1.25.0 (introduced in commit d1d631a, PR #1015)\n\nThe root cause is in `lib/policy/checker.go`, `PathChecker.Check()`:\n```go\nfunc (pc *PathChecker) Check(r *http.Request) (bool, error) {\n    originalUrl := r.Header.Get(\"X-Original-URI\")\n    if originalUrl != \"\" {\n        if pc.regexp.MatchString(originalUrl) {\n            return true, nil\n        }\n    }\n    if pc.regexp.MatchString(r.URL.Path) {\n        return true, nil\n    }\n    return false, nil\n}\n```\n\nThe header value comes directly from the client request. The middleware chain never strips it. In reverse proxy mode an attacker fully controls it.\nThe default policy imports `data/common/keep-internet-working.yaml`, which contains path-only ALLOW rules with no other conditions:\n\n```yaml\n- name: well-known\n  path_regex: ^/\\.well-known/.*$\n  action: ALLOW\n```\n\nWhen `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.\n\n\n# Proof of concept\n\nNormal request, gets challenged:\n```\ncurl -s https://anubis.techaro.lol/ | grep -o \"<title>.*</title>\"\n```\n\nBypass, gets upstream content:\n```\ncurl -s -H \"X-Original-URI: /.well-known/x\" https://anubis.techaro.lol/ | grep -o \"<title>.*</title>\"\n```\n\nThe 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.\n\n# Suggested fix\nThe fix should probably be to strip the header from incoming client requests in the middleware chain before policy evaluation. In `auth_request` mode the header is set by the proxy after Anubis processes the middleware, so stripping it at ingress does not break that deployment mode.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/TecharoHQ/anubis"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.22.0"
      }, {
        "fixed" : "1.26.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/TecharoHQ/anubis/security/advisories/GHSA-6wcg-mqvh-fcvg"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-62314"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/TecharoHQ/anubis/pull/1630"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/TecharoHQ/anubis/commit/276b537776b281b1c4e01421435bc03ade3d8fc4"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/TecharoHQ/anubis"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/TecharoHQ/anubis/releases/tag/v1.26.0-pre1"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-284" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-10-02T18:22:08Z",
    "nvd_published_at" : "2026-07-15T22:17:38Z"
  }
}