CVE-2026-94040: vas3k TaxHacker · Server-Side Request Forgery
Affects vas3k TaxHackerSource CVE Database V5
Public exploit available · CVSS 6.9 Medium · patch available : patch vas3k TaxHacker as a priority.
Data as of 5 Nov 2026, 00:01 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 20 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| vas3kTaxHacker | Affected
| Fixed in– |
GitHubvas3k/TaxHackerpkg:github/vas3k/TaxHackerOther threats | Affected
| Fixed in– |
CPE configurations (1)
cpe:2.3:a:vas3k:taxhacker:*:*:*:*:*:*:*:*
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available for this vulnerability. Since vas3k TaxHacker is a cloud-hosted service, the vendor is responsible for applying the fix. Users should verify with the vendor that the patch has been applied or follow vendor advisories for remediation status. No additional mitigation steps are indicated by the vendor advisory.
Description
A flaw has been found in vas3k TaxHacker up to 0.8.5. Affected by this vulnerability is the function testLLMProviderAction of the file app/(app)/apps/settings/actions.ts. Executing a manipulation of the argument provider/apiKey/model/baseUrl can lead to server-side request forgery. The attack may be performed from remote. The exploit has been published and may be used. The project was informed of the problem early through an issue report but has not responded yet.