PatchSiren cyber security CVE debrief
CVE-2026-94040 vas3k CVE debrief
A server-side request forgery vulnerability has been identified in vas3k TaxHacker up to version 0.8.5. The issue affects the testLLMProviderAction function in the file app/(app)/apps/settings/actions.ts. This function can be manipulated through the provider, apiKey, model, and baseUrl arguments, potentially allowing for unauthorized requests to be made from the server. The vulnerability has been publicly disclosed and an exploit has been published, but the project has not yet responded to the issue report.
- Vendor
- vas3k
- Product
- TaxHacker
- CVSS
- MEDIUM 5.5
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-20
- Original CVE updated
- 2026-09-20
- Advisory published
- 2026-09-20
- Advisory updated
- 2026-09-20
Who should care
Defenders responsible for systems using vas3k TaxHacker up to version 0.8.5 should assess their exposure and prioritize verifying the presence of this vulnerability in their systems.
Why it matters
Defenders should care about this vulnerability because it can lead to unauthorized requests from the server, potentially resulting in data breaches or system compromise. They should verify the presence of this vulnerability in their systems and prioritize patch application or mitigation.
- Potential unauthorized requests from the server
- Possible data breaches or system compromise
- Need for verification of vulnerability presence and patch application
Technical summary
The testLLMProviderAction function in the file app/(app)/apps/settings/actions.ts is vulnerable to server-side request forgery. The function can be manipulated through the provider, apiKey, model, and baseUrl arguments, potentially allowing for unauthorized requests to be made from the server. This vulnerability affects vas3k TaxHacker up to version 0.8.5 and has been publicly disclosed, with an exploit published. Defenders should assess their exposure and prioritize verifying the presence of this vulnerability in their systems.
Defensive priority
Defenders should prioritize verifying the presence of this vulnerability in their systems and applying patches or mitigations as soon as they become available.
Recommended defensive actions
- Verify the presence of this vulnerability in your systems
- Monitor for patches or mitigations from the vendor
- Implement compensating controls to prevent unauthorized requests
- Review system logs for suspicious activity
- Conduct a thorough risk assessment of exposed systems
- Prioritize patch application for critical systems
- Document and track remediation efforts
Evidence notes
The CVE record and NVD entry provide details about the vulnerability, including its description, CVSS score, and affected versions. However, the vendor has not yet responded to the issue report, and there is no information on official patches or mitigations.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-94040 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-94040
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-94040 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-94040
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/vas3k/TaxHacker/
-
Source reference
Unverified legacy reference
URL: https://github.com/vas3k/TaxHacker/issues/187
-
Source reference
Unverified legacy reference
URL: https://vuldb.com/cve/CVE-2026-94040
-
Source reference
Unverified legacy reference
URL: https://vuldb.com/submit/947879
-
Source reference
Unverified legacy reference
URL: https://vuldb.com/vuln/407969
-
Source reference
Unverified legacy reference
URL: https://vuldb.com/vuln/407969/cti
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.