How severe is GHSA-529f-9qwm-9628?

No CVSS score has been assigned to GHSA-529f-9qwm-9628 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-529f-9qwm-9628?

GHSA-529f-9qwm-9628 affects the following packages: tinacms (npm), @tinacms/cli (npm), @tinacms/graphql (npm). Ecosystems affected: npm.

How do I fix GHSA-529f-9qwm-9628?

Update tinacms to 3.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-529f-9qwm-9628 is resolved across your whole dependency graph.

How do I detect GHSA-529f-9qwm-9628 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for tinacms. 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.

How do I mitigate GHSA-529f-9qwm-9628 if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-529f-9qwm-9628?

O3 pinpoints whether GHSA-529f-9qwm-9628 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-529f-9qwm-9628 actively exploited in the wild?

No public exploit code has been indexed for GHSA-529f-9qwm-9628 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-529f-9qwm-9628?

GHSA-529f-9qwm-9628 is classified as Code Injection (CWE-94). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-529f-9qwm-9628 published, and has it been updated?

GHSA-529f-9qwm-9628 was published on December 18, 2025 and was last updated on December 18, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-529f-9qwm-9628

Fix: tinacms/tinacms@fa7c27a

GHSA-529f-9qwm-9628 is a Code Injection vulnerability in tinacms. O3 Security confirms whether GHSA-529f-9qwm-9628 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

tinacms is vulnerable to arbitrary code execution

Also known asCVE-2025-68278

Published

Dec 18, 2025

Updated

Dec 18, 2025

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Real-World Exposure

3 pkgs affected

📦tinacms📦@tinacms/cli📦@tinacms/graphql

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

Summary

tinacms uses the gray-matter package in an insecure way allowing attackers that can control the content of the processed markdown files, e.g., blog posts, to execute arbitrary code.

Details

The gray-matter package executes by default the code in the markdown file's front matter. tinacms does not change this behavior when process markdown file, e.g., by passing a custom engine property for js/javascript in the options object.

PoC

Create a tinacms app using the cli/documentation:

npx create-tina-app@latest

Modify one of the blog posts to contain the following front matter:

---js
{
  "title": "Pawned" + console.log(require("fs").readFileSync("/etc/passwd").toString())
}
---

Start the tinacms server, e.g., with npm run dev
Observe the console of the server printing the password file, showing that attackers can execute arbitrary commands.

Impact

RCE: attackers can execute arbitrary JavaScript code on the server hosting tinacms.

Feasibility

Potential attack scenarios can be executed like this: Companies often have technical writers as contractors. These contractors produce md files, which they send over email or upload in a shared cloud folder. Developers download these files and upload them in tinacms's content folder. While this example might appear speculative or contrived, a general observation is that developers would be very surprised to find out that processing untrusted markdown files via tinacms = server-side code execution = complete machine take over. That is, tinacms users might not expect markdown files to contain anything else than data and gray-matter violates that assumption.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`tinacms`	all versions	3.1.1
📦npm	`@tinacms/cli`	all versions	2.0.4
📦npm	`@tinacms/graphql`	all versions	2.0.3

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for tinacms. 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 to 3.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-529f-9qwm-9628 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-529f-9qwm-9628 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-529f-9qwm-9628. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary ```tinacms``` uses the ```gray-matter``` package in an insecure way allowing attackers that can control the content of the processed markdown files, e.g., blog posts, to execute arbitrary code. ### Details The ```gray-matter``` package executes by default the code in the markdown file's front matter. ```tinacms``` does not change this behavior when process markdown file, e.g., by passing a custom engine property for js/javascript in the options object. ### PoC 1. Create a tinacms app using the cli/documentation: ``` npx create-tina-app@latest ``` 2. Modify one of the blog posts

O3 Security · Impact-Aware SCA

Is GHSA-529f-9qwm-9628 in your dependencies?

O3 detects GHSA-529f-9qwm-9628 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works