# CVE-2026-36758: Server-side request forgery in n/a

> Authenticated attackers can scan internal resources via SSRF in Halo CMS, potentially exposing sensitive internal network information.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Apr 2026
- **Updated:** 30 Apr 2026
- **Also known as:** GHSA-j2q6-4wwg-vm5c

## What is CVE-2026-36758?

CVE-2026-36758 is a medium-severity server-side request forgery vulnerability in n/a, published on 30 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A Server-Side Request Forgery (SSRF) in the /themes/-/install-from-uri endpoint of halo v2.22.14 allows authenticated attackers to scan internal resources via a crafted GET request.

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

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


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

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

## Is CVE-2026-36758 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-36758 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-36758 is a medium-severity server-side request forgery vulnerability in n/a, published on 30 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-36758 exists.

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

## Sources

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

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