PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-66005 janhq CVE debrief

CVE-2026-66005 is a medium-severity vulnerability in Jan through version 0.8.4, caused by a CORS misconfiguration in its local API server. This issue allows network-adjacent attackers to bypass trusted host restrictions by exploiting the server's replacement of user-configured trusted hosts with a wildcard that reflects arbitrary origins with credentials. Attackers on the local network or using DNS rebinding can reach the unauthenticated OpenAI-compatible API to perform inference, enumerate models, invoke MCP tools, and read cross-origin responses.

Vendor
janhq
Product
jan
CVSS
MEDIUM 5.3
CISA KEV
Not listed in stored evidence
Original CVE published
2026-07-24
Original CVE updated
2026-09-17
Advisory published
2026-07-24
Advisory updated
2026-09-17

Who should care

Defenders responsible for Jan installations, particularly those exposed to local networks or using DNS rebinding techniques, should assess their exposure and prioritize remediation.

Why it matters

CVE-2026-66005 is a medium-severity vulnerability in Jan that allows network-adjacent attackers to bypass trusted host restrictions and access the unauthenticated OpenAI-compatible API. Defenders should prioritize verifying and remediating this vulnerability in Jan installations, particularly those exposed to local networks or using DNS rebinding techniques.

  • Network-adjacent attackers can bypass trusted host restrictions
  • Unauthenticated access to OpenAI-compatible API for inference, model enumeration, MCP tools, and cross-origin response reading
  • Potential for DNS rebinding attacks

Technical summary

The vulnerability is caused by a CORS misconfiguration in the local API server of Jan through version 0.8.4. The server replaces user-configured trusted hosts with a wildcard that reflects arbitrary origins with credentials, allowing network-adjacent attackers to bypass trusted host restrictions. This issue allows attackers on the local network or using DNS rebinding to reach the unauthenticated OpenAI-compatible API to perform inference, enumerate models, invoke MCP tools, and read cross-origin responses. Defenders should prioritize verifying and remediating this vulnerability in Jan installations, particularly those exposed to local networks or using DNS rebinding techniques, by reviewing and updating CORS,

Defensive priority

Defenders should prioritize verifying and remediating this vulnerability in Jan installations, particularly those exposed to local networks or using DNS rebinding techniques.

Recommended defensive actions

  • Verify Jan version and check for exposure to local networks or DNS rebinding techniques
  • Review and update CORS configuration to restrict trusted hosts
  • Monitor API server logs for suspicious activity
  • Apply the fix from commit 3e1c1e7
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its description, CVSS score, and affected versions. However, the exact scope of affected deployments and potential impact require further verification.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-66005 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-66005

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-66005 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-66005

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

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.