GHSA-pc2q-jcxq-rjrr
HIGHGHSA-pc2q-jcxq-rjrr is a high-severity (CVSS 8.6) Information Exposure vulnerability in @tinacms/cli. O3 Security confirms whether GHSA-pc2q-jcxq-rjrr is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Sensitive Information leak via Script File in TinaCMS
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
@tinacms/clinpmDescription
Impact
Sensitive Information leaked via script File in TinaCMS. Sites building with @tinacms/cli >= 1.0.0 && < 1.0.9 that store sensitive values in process.env var are impacted. If you're on a version prior to 1.0.0 this vulnerability does not affect you.
If your Tina-enabled website has sensitive credentials stored as environment variables (eg. Algolia API keys) you should rotate those keys immediately.
Patches
This issue has been patched in @tinacms/[email protected]
Workarounds
Upgrading, and rotating secure & exposed keys is required for the proper fix.
References
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @tinacms/cli | ≥ 1.0.0&&< 1.0.9 | 1.0.9 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @tinacms/cli. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update @tinacms/cli to 1.0.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pc2q-jcxq-rjrr is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-pc2q-jcxq-rjrr is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-pc2q-jcxq-rjrr. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-pc2q-jcxq-rjrr in your dependencies?
O3 detects GHSA-pc2q-jcxq-rjrr across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.