CVE-2026-27812: Wei-Shaw sub2api · Improper Encoding or Escaping of Output
Affects Wei-Shaw sub2apiSource CVE Database V5
Not known to be exploited · CVSS 8.0 High : upgrade to 0.1.85 soon.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.1.85
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:UExploitation evidence
Disclosed: evidence found.
CVE published 26 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade sub2api and wei-shaw/sub2api to 0.1.85.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Wei-Shawsub2api | Affected
| Fixed in
|
GitHubwei-shaw/sub2apipkg:github/wei-shaw/sub2apiOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
- Upgrade sub2api to version 0.1.85 or later immediately to apply the official fix that properly validates and encodes headers in password reset links.
- If upgrading is not feasible immediately, disable the 'forgot password' feature to prevent attackers from exploiting the password reset endpoint.
- Implement strict validation and sanitization of Host and Forwarded headers at the web server or application gateway level to reject suspicious or unexpected header values.
- Monitor logs for unusual password reset requests or anomalies in header values that could indicate exploitation attempts.
- Educate users to verify URLs in password reset emails and report suspicious links.
- Consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block header injection attempts targeting password reset functionality.
- After patching, conduct penetration testing focused on header manipulation to ensure the vulnerability is fully remediated.
- Review and enhance overall API gateway security posture, including rate limiting and anomaly detection, to mitigate abuse of password reset and other sensitive endpoints.
Description
Sub2API is an AI API gateway platform designed to distribute and manage API quotas from AI product subscriptions. A vulnerability in versions prior to 0.1.85 is a Password Reset Poisoning (Host Header / Forwarded Header trust issue), which allows attackers to manipulate the password reset link. Attackers can exploit this flaw to inject their own domain into the password reset link, leading to the potential for account takeover. The vulnerability has been fixed in version v0.1.85. If upgrading is not immediately possible, users can mitigate the vulnerability by disabling the "forgot password" feature until an upgrade to a patched version can be performed. This will prevent attackers from exploiting the vulnerability via the affected endpoint.