# CVE-2026-119709: Grimoire before 1.0.0 Unauthenticated SSRF via /api/fetch-metadata


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 30 Oct 2026
- **Updated:** 30 Oct 2026
- **Also known as:** GHSA-v3p4-vhx3-fmh5

## What is CVE-2026-119709?

CVE-2026-119709 is a medium-severity vulnerability in goniszewski grimoire, published on 30 Oct 2026. 

### Official description

Grimoire before 1.0.0 contains an unauthenticated server-side request forgery vulnerability in the /api/fetch-metadata POST handler that passes user-supplied URLs to getMetadata() without authentication checks. Attackers can submit URLs targeting loopback, internal-network, or cloud metadata endpoints and read the parsed title, description, and page content returned.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

No fix has been published for CVE-2026-119709 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-119709 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-119709 is a medium-severity vulnerability in goniszewski grimoire, published on 30 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-119709 in the wild and no public exploit code.

Affected product: goniszewski grimoire. 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-119709/ (Markdown: https://insights.sbomify.com/CVE-2026-119709/index.md)
```

## Sources

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

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