Vulnerability in github.com/TecharoHQ/anubis (CVE-2026-62314)
Summary
Vulnerability in github.com/TecharoHQ/anubis (CVE-2026-62314). Risk of unauthorized operations or information disclosure. Exploitable via auth_request. Mitigation: upgrade to 1.26.0 or later.
Original description
The description as published by the source.
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():
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:
- 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 ".*"
Bypass, gets upstream content:
curl -s -H "X-Original-URI: /.well-known/x" https://anubis.techaro.lol/ | grep -o ".*"
The first command returns the Anubis challenge page title. The second returns the real site title directly…
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-62314 has been found in github.com/TecharoHQ/anubis.
Attackers can target a specific entry point like auth_request over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.8/10.
What to do: upgrade github.com/TecharoHQ/anubis to 1.26.0 or later.
If unsure, ask your IT team or search "github.com/TecharoHQ/anubis CVE-2026-62314" on the vendor's site.
CVE-2026-62314 (github.com/TecharoHQ/anubis) — CWE-284 / CVSS v3 5.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: auth_request
Patched: 1.26.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-284) exists in github.com/TecharoHQ/anubis. Attackers reach the vulnerable code path via auth_request without authentication.
Check the vendor advisory for the affected versions of github.com/TecharoHQ/anubis. Attack surface: auth_request.
Severity: Medium (CVSS 5.8/10). Risk of unauthorized operations or information disclosure.
Update to 1.26.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/TecharoHQ/anubis' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/TecharoHQ/anubis' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/TecharoHQ/anubisを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/TecharoHQ/anubis to 1.26.0ステージング環境で 1.26.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com