{"answers":{"affected":"2 open source packages ship an affected version, including @tinacms/graphql. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34604 exists.","fix":"Upgrade @tinacms/graphql to 2.2.2 or later.","what":"CVE-2026-34604 is a high-severity path traversal vulnerability in tinacms, published on 1 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-34604 and fix it if it is affected.\n\nWhat it is: CVE-2026-34604 is a high-severity path traversal vulnerability in tinacms, published on 1 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34604 exists.\n\nAffected packages and fixed versions:\n- @tinacms/graphql (npm): affected all versions; fixed in 2.2.2\n- @tinacms/graphql (npm): affected all versions; fixed in 2.2.2\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-34604/ (Markdown: https://insights.sbomify.com/CVE-2026-34604/index.md)","id":"CVE-2026-34604","markdown":"https://insights.sbomify.com/CVE-2026-34604/index.md","name":"CVE-2026-34604","record":{"aliases":["GHSA-g9c2-gf25-3x67"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"TinaCMS GraphQL library","requires_auth":"low_privilege","summary":"Attackers can bypass path validation via symlinks to read, modify, or delete files outside the intended content root in TinaCMS.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"tinacms\\/graphql","vendor":"ssw"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-59","name":"Improper Link Resolution Before File Access"},{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Tina is a headless content management system. Prior to version 2.2.2, @tinacms/graphql uses string-based path containment checks in FilesystemBridge. That blocks plain ../ traversal, but it does not resolve symlink or junction targets. If a symlink/junction already exists under the allowed content root, a path like content/posts/pivot/owned.md is still considered \"inside\" the base even though the real filesystem target can be outside it. As a result, FilesystemBridge.get(), put(), delete(), and glob() can operate on files outside the intended root. This issue has been patched in version 2.2.2.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"@tinacms/graphql's `FilesystemBridge` Path Validation Can Be Bypassed via Symlinks or Junctions","id":"CVE-2026-34604","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"SiYuan: Reflected XSS via SVG namespace prefix bypass in SanitizeSVG ( getDynamicIcon, unauthenticated )","id":"CVE-2026-34605"},"packages":[{"ecosystem":"npm","fixed":["2.2.2"],"introduced":["0"],"last_affected":[],"package":"@tinacms/graphql","purl":null,"source":"GHSA-g9c2-gf25-3x67"},{"ecosystem":"npm","fixed":["2.2.2"],"introduced":["0"],"last_affected":[],"package":"@tinacms/graphql","purl":"pkg:npm/%40tinacms/graphql","source":"GHSA-g9c2-gf25-3x67"}],"prev":{"headline":"@tinacms/graphql's Media Endpoints Can Escape the Media Root via Symlinks or Junctions","id":"CVE-2026-34603"},"products":["tinacms"],"published":"2026-04-01","related":[{"cvss_score":8.1,"headline":"@tinacms/graphql has Path Traversal that leads to overwrite of arbitrary files","id":"CVE-2026-33949","kev_date_added":null,"published":"2026-04-01"},{"cvss_score":6.3,"headline":"Path Traversal in @tinacms/graphql","id":"CVE-2026-24125","kev_date_added":null,"published":"2026-03-12"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-04-01","vendors":["tinacms"]},"summary":"Attackers can bypass path validation via symlinks to read, modify, or delete files outside the intended content root in TinaCMS.","url":"https://insights.sbomify.com/CVE-2026-34604/"}