For your digest
@tinacms/graphql: @tinacms/graphql's `FilesystemBridge` Path Validation Can Be Bypassed via Symlinks or Junctions
It touches something Phylax follows. No evidence of use yet.
Does it affect what I run?
@tinacms/graphql (npm)
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- @tinacms/graphql (npm): every version, before 2.2.2
The fix
@tinacms/graphql (npm) fixed in 2.2.2
npmnpm install "@tinacms/graphql@2.2.2"pnpmpnpm add "@tinacms/graphql@2.2.2"yarnyarn add "@tinacms/graphql@2.2.2"bunbun add "@tinacms/graphql@2.2.2"Check what is installednpm ls @tinacms/graphqlPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency @tinacms/graphql to 2.2.2 or the nearest later release, to fix CVE-2026-34604. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
Fix commands generated from the advisory's versions. No model wrote them.
In plain words
Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.
Evidence
No evidence that it is being used, or can be. It is listed because of what it affects.
Timeline
- First published here, as "For your digest".
- Level changed from "For your digest" to "This week".
- Evidence added: CISA's assessment in the CVE record says a proof of concept is public. (CISA Vulnrichment (SSVC and KEV fields inside CVE records))
- Level changed from "This week" to "For your digest".
- Evidence withdrawn: CISA's assessment in the CVE record says a proof of concept is public. (CISA Vulnrichment (SSVC and KEV fields inside CVE records))