{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-81664 exists.","fix":"No fix has been published for CVE-2026-81664 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-81664 is a medium-severity missing authorization vulnerability in openfaas faas, 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-81664 and fix it if it is affected.\n\nWhat it is: CVE-2026-81664 is a medium-severity missing authorization vulnerability in openfaas faas, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-81664 exists.\n\nAffected product: openfaas faas. 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-81664/ (Markdown: https://insights.sbomify.com/CVE-2026-81664/index.md)","id":"CVE-2026-81664","markdown":"https://insights.sbomify.com/CVE-2026-81664/index.md","name":"CVE-2026-81664","record":{"aliases":["GHSA-gwq3-cphc-pwmg"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"OpenFaaS Gateway","requires_auth":"none","summary":"Unauthenticated attackers can access telemetry data via the /system/telemetry route, exposing resource metrics and cluster state.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"The OpenFaaS gateway registers GET /system/telemetry in gateway/main.go and, when basic_auth is enabled, wraps each administrative /system/* handler in auth.DecorateWithBasicAuth. TelemetryHandler was left out of that wrap block from 0.27.11, which introduced the route, until 0.27.14, which added it. On an affected gateway the route therefore reaches the forwarding proxy with no credential check and returns whatever the configured provider serves for /system/telemetry, so any client that can reach the gateway port can read the provider's telemetry regardless of the basic_auth setting. The exposed content depends on the provider, and covers resource and invocation metrics for faasd and pod or cluster state for faas-netes.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"OpenFaaS Gateway 0.27.11 through 0.27.13 Missing Authentication on the /system/telemetry Route","id":"CVE-2026-81664","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"Corosync: corosync: heap-based buffer overflow in totempg assembly buffer during fragmented message reassembly","id":"CVE-2026-81665"},"packages":[],"prev":{"headline":"Flowintel Alert Settings Configuration Allows Remote Code Execution via Arbitrary Configuration Keys","id":"CVE-2026-81662"},"products":["faas"],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-31","vendors":["openfaas"]},"summary":"Unauthenticated attackers can access telemetry data via the /system/telemetry route, exposing resource metrics and cluster state.","url":"https://insights.sbomify.com/CVE-2026-81664/"}