# CVE-2026-15525: kLOsk adloop write.py _validate_urls server-side request forgery

> Remote attackers can exploit a server-side request forgery vulnerability in the adloop library's URL validation function to access internal resources.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **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:** 13 Jul 2026
- **Updated:** 13 Jul 2026
- **Also known as:** GHSA-cvvx-wcx7-g65m

## What is CVE-2026-15525?

CVE-2026-15525 is a medium-severity server-side request forgery vulnerability in kLOsk adloop, published on 13 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was detected in kLOsk adloop up to 0.9.0. This vulnerability affects the function _validate_urls of the file src/adloop/ads/write.py. Performing a manipulation of the argument final_url results in server-side request forgery. The attack may be initiated remotely. The exploit is now public and may be used. Upgrading to version 0.10.0 is able to resolve this issue. The patch is named 217399723e3a2fb39389e5355d49ed80aaf9ea7c. Upgrading the affected component is advised.

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

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


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

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

## Is CVE-2026-15525 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-15525 is a medium-severity server-side request forgery vulnerability in kLOsk adloop, published on 13 Jul 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-15525 exists.

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

## Sources

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

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