PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-81099 timescale CVE debrief

CVE-2026-81099 is a DNS rebinding vulnerability in the tiger-slack project. The MCP HTTP transport was started without enabling the host allow-list provided by the underlying SDK, allowing requests from any host. This issue was fixed by passing the DNS-rebinding-protection option explicitly alongside a dependency update. The vulnerability allows for DNS rebinding attacks, which could lead to unauthorized access. Defenders should prioritize verifying the affected versions and applying the fix.

Vendor
timescale
Product
tiger-slack
CVSS
HIGH 7.6
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-27
Original CVE updated
2026-09-23
Advisory published
2026-08-27
Advisory updated
2026-09-23

Who should care

Defenders responsible for the tiger-slack project and its dependencies should assess exposure and apply the fix to prevent DNS rebinding attacks. Defenders should verify the affected versions and apply the fix to prevent DNS rebinding attacks. The vulnerability allows for DNS rebinding attacks, which could lead to unauthorized access.

Why it matters

CVE-2026-81099 is a DNS rebinding vulnerability in the tiger-slack project that allows for unauthorized access. Defenders should prioritize verifying the affected versions and applying the fix.

  • Defenders should verify the affected versions and apply the fix to prevent DNS rebinding attacks
  • The vulnerability allows for DNS rebinding attacks, which could lead to unauthorized access

Technical summary

The tiger-slack project started its MCP HTTP transport without enabling the host allow-list provided by the underlying SDK. The mcp/src/httpServer.ts file called the shared httpServerFactory helper and never set the DNS-rebinding-protection option, allowing requests from any host. A page in a browser could point a name it controlled at the address the server was bound to and drive the locally reachable Slack MCP server through the visitor's browser.

Defensive priority

Defenders should prioritize verifying the affected versions and applying the fix, as the vulnerability allows for DNS rebinding attacks.

Recommended defensive actions

  • Verify the affected versions of the tiger-slack project
  • Apply the fix by passing the DNS-rebinding-protection option explicitly
  • Review the dependency update and ensure it is applied
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
  • 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, but the affected versions and scope of impact require further verification. The tiger-slack project started its MCP HTTP transport without enabling the host allow-list provided by the underlying SDK. The mcp/src/httpServer.ts file called the shared httpServerFactory helper and never set the DNS-rebinding-protection option, allowing requests from any host. A page in a browser could point a name it controlled at the address the server was bound to and drive the locally

Sources and references

Verified primary and authoritative sources

  • CVE-2026-81099 CVE Program record

    Publisher, destination, and source semantics verified

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

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

  • CVE-2026-81099 NVD vulnerability detail

    Publisher, destination, and source semantics verified

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

    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.