# CVE-2026-130743: Grav 2.0.0 before 2.2.18 RCE and File Read via Blueprint Files


- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 18 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** GHSA-3x2v-6jqq-7gq8, GHSA-9hrq-9p5w-qh7j

## What is CVE-2026-130743?

CVE-2026-130743 is a high-severity vulnerability in getgrav grav, published on 18 Nov 2026. 

### Official description

Grav from 2.0.0 before 2.2.18 contains an insecure blueprint trust vulnerability that allows publisher accounts to read secrets and execute PHP by planting or selecting attacker-controlled blueprint files. Attackers can abuse the import@ directive, uploaded YAML media named as the page template, or form.flash_folder to leak password hashes and keys or invoke static PHP methods for code execution.

Weakness: CWE-73 (External Control of File Name or Path)

## Which versions are affected by CVE-2026-130743?


## How do I fix CVE-2026-130743?

Upgrade getgrav grav to 2.2.18 or later. The advisory says that version fixes it.

## Is CVE-2026-130743 being exploited?

There is no known exploitation of CVE-2026-130743 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-130743 and fix it if it is affected.

What it is: CVE-2026-130743 is a high-severity vulnerability in getgrav grav, published on 18 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-130743 in the wild and no public exploit code.

Affected product: getgrav grav. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-130743/ (Markdown: https://insights.sbomify.com/CVE-2026-130743/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-130743
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-130743
- OSV: https://osv.dev/vulnerability/CVE-2026-130743

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-130743/
Summaries are generated and may contain mistakes; the official description above is the record.
