{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-81095 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-81095 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-81095 is a high-severity server-side request forgery vulnerability in timescale pg-aiguide, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-81095 and fix it if it is affected.\n\nWhat it is: CVE-2026-81095 is a high-severity server-side request forgery vulnerability in timescale pg-aiguide, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-81095 in the wild and no public exploit code.\n\nAffected product: timescale pg-aiguide. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-81095/ (Markdown: https://insights.sbomify.com/CVE-2026-81095/index.md)","id":"CVE-2026-81095","markdown":"https://insights.sbomify.com/CVE-2026-81095/index.md","name":"CVE-2026-81095","record":{"aliases":["GHSA-x76c-qpjv-crcp"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Timescale pg-aiguide","requires_auth":"none","summary":"Attackers can bypass host header restrictions to access local MCP servers via DNS rebinding, requiring a patch to enable built-in protections.","user_interaction":"required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":7.6,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-346","name":"Origin Validation Error"}],"description":"pg-aiguide started its MCP HTTP transport without enabling the host allow-list the underlying SDK provides. src/httpServer.ts called the shared httpServerFactory helper and never set the DNS-rebinding-protection option, so the transport accepted a request whatever host it named. A page in a browser could therefore point a name it controlled at the address the server was bound to and drive the locally reachable MCP server through the visitor's browser. The protection was already available in the packaged transport and simply not turned on, so updating the dependency alone would not have closed it. Version 0.5.1 passes the option explicitly.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Timescale pg-aiguide through 0.5.0 DNS Rebinding via Disabled Host Header Allow-List","id":"CVE-2026-81095","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"ToolUniverse through 1.2.6 Unauthenticated Remote Code Execution via python_code_executor Sandbox Escape","id":"CVE-2026-81096"},"packages":[],"prev":{"headline":"mcp-router CLI before 0.6.3 Binds the MCP Aggregator to All Interfaces Without Requiring Authentication","id":"CVE-2026-81094"},"products":["pg-aiguide"],"published":"2026-08-27","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-29","vendors":["timescale"]},"summary":"Attackers can bypass host header restrictions to access local MCP servers via DNS rebinding, requiring a patch to enable built-in protections.","url":"https://insights.sbomify.com/CVE-2026-81095/"}