{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-81093 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-81093 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-81093 is a high-severity server-side request forgery vulnerability in apify actors-mcp-server, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-81093 and fix it if it is affected.\n\nWhat it is: CVE-2026-81093 is a high-severity server-side request forgery vulnerability in apify actors-mcp-server, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-81093 in the wild and no public exploit code.\n\nAffected product: apify actors-mcp-server. 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-81093/ (Markdown: https://insights.sbomify.com/CVE-2026-81093/index.md)","id":"CVE-2026-81093","markdown":"https://insights.sbomify.com/CVE-2026-81093/index.md","name":"CVE-2026-81093","record":{"aliases":["GHSA-gghj-77w7-6r3h","GHSA-m28f-9v8h-gg2f"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Apify MCP Server","requires_auth":"none","summary":"Attackers can exploit Server-Side Request Forgery in Apify Actors MCP Server to access internal network resources and cloud instance metadata.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"The get-html-skeleton tool fetched a URL the caller supplied after checking only its syntax. The handler in src/tools/common/get_html_skeleton.ts validated the url argument with isValidHttpUrl from src/utils/generic.ts, which confirmed the string began with an http or https scheme and parsed as a URL and inspected neither the host name nor the address it resolves to. Loopback, link-local and private ranges therefore passed, including the address cloud providers use to serve instance metadata. The unchecked URL was handed to the web-browser actor and the fetched document was returned in the tool response, so any caller of the MCP server could make it request an endpoint reachable only from the host and read the result, including instance credentials. Version 0.9.12 removes the tool.","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":"Apify Actors MCP Server before 0.9.12 Server-Side Request Forgery via get-html-skeleton","id":"CVE-2026-81093","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"mcp-router CLI before 0.6.3 Binds the MCP Aggregator to All Interfaces Without Requiring Authentication","id":"CVE-2026-81094"},"packages":[],"prev":{"headline":"mcp-go before 0.56.0 Missing Host Header Validation Enables DNS Rebinding","id":"CVE-2026-81092"},"products":["actors-mcp-server"],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-29","vendors":["apify"]},"summary":"Attackers can exploit Server-Side Request Forgery in Apify Actors MCP Server to access internal network resources and cloud instance metadata.","url":"https://insights.sbomify.com/CVE-2026-81093/"}