# CVE-2026-117565: Artalk before 2.10.1 Unauthenticated SSRF via Comment Page Title Fetch


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

## What is CVE-2026-117565?

CVE-2026-117565 is a medium-severity vulnerability in ArtalkJS Artalk, published on 27 Oct 2026. 

### Official description

Artalk before 2.10.1 contains an unauthenticated server-side request forgery vulnerability that allows remote attackers to make the server fetch arbitrary URLs by submitting anonymous comments to /api/v2/comments. Attackers can set a page_key to an internal URL, which GetTitleByURL fetches after only scheme validation, then read the page title through the public comment list.

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

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


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

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

## Is CVE-2026-117565 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-117565 is a medium-severity vulnerability in ArtalkJS Artalk, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-117565 in the wild and no public exploit code.

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

## Sources

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

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