What is CVE-2025-64716?

CVE-2025-64716 is a medium-severity cross-site scripting (XSS) vulnerability in github.com/TecharoHQ/anubis (go), affecting versions < 1.23.0. It is fixed in 1.23.0. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.

Which versions of github.com/TecharoHQ/anubis are affected by CVE-2025-64716?

github.com/TecharoHQ/anubis (go) versions < 1.23.0 is affected.

Is there a fix for CVE-2025-64716?

Yes. CVE-2025-64716 is fixed in 1.23.0. Upgrade to this version or later.

Is CVE-2025-64716 exploitable, and should I be worried?

Whether CVE-2025-64716 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2025-64716 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2025-64716 in github.com/TecharoHQ/anubis

Q: Which versions of github.com/TecharoHQ/anubis are affected by CVE-2025-64716?

github.com/TecharoHQ/anubis (go) versions < 1.23.0 is affected.

Q: Is there a fix for CVE-2025-64716?

Yes. CVE-2025-64716 is fixed in 1.23.0. Upgrade to this version or later.

Q: Is CVE-2025-64716 exploitable, and should I be worried?

Whether CVE-2025-64716 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2025-64716 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2025-64716?

Upgrade github.com/TecharoHQ/anubis to 1.23.0 or later.

Summary

Anubis vulnerable to possible XSS via redir parameter when using subrequest auth mode

When using subrequest authentication, Anubis did not perform validation of the redirect URL and redirects user to any URL scheme. While most modern browsers do not allow a redirect to javascript: URLs, it could still trigger dangerous behavior in some cases.

GET https://example.com/.within.website/?redir=javascript:alert() responds with Location: javascript:alert().

Note

This was originally reported by @mbiesiad against Weblate.

Impact

Anybody with a subrequest authentication seems affected. Using javascript: URLs will probably be blocked by most modern browsers, but using custom protocols for third-party applications might still trigger dangerous operations.

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

Affected versions

github.com/TecharoHQ/anubis (< 1.23.0)

Security releases

github.com/TecharoHQ/anubis → 1.23.0 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade github.com/TecharoHQ/anubis to 1.23.0 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2025-64716? CVE-2025-64716 is a medium-severity cross-site scripting (XSS) vulnerability in github.com/TecharoHQ/anubis (go), affecting versions < 1.23.0. It is fixed in 1.23.0. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
Which versions of github.com/TecharoHQ/anubis are affected by CVE-2025-64716? github.com/TecharoHQ/anubis (go) versions < 1.23.0 is affected.
Is there a fix for CVE-2025-64716? Yes. CVE-2025-64716 is fixed in 1.23.0. Upgrade to this version or later.
Is CVE-2025-64716 exploitable, and should I be worried? Whether CVE-2025-64716 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2025-64716 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2025-64716? Upgrade github.com/TecharoHQ/anubis to 1.23.0 or later.