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.
CVE-2026-15525
This medium-severity CVE scores 6.3 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.3
- EG Score
- 6.3(low)
- EPSS
- —
- KEV
- Not listed
Published
July 13, 2026
Last Modified
July 13, 2026
Advisory Details (4)
Auto-updated Jul 13, 2026v0.10.0 — bring your own Google Cloud project (bundled OAuth retired)
Patch available: kLOsk/adloop v0.10.0
https://github.com/kLOsk/adloop/releases/tag/v0.10.0[Potential Vulnerability] adloop fetches a caller-controlled URL with no scheme/host validation — SSRF + local-file access via `final_url` · Issue #41 · kLOsk/adloop · GitHub
https://github.com/kLOsk/adloop/issues/41commit 217399723e3a (kLOsk/adloop)
Patch available: kLOsk/adloop v0.10.0 (contains commit 217399723e3a)
https://github.com/kLOsk/adloop/commit/217399723e3a2fb39389e5355d49ed80aaf9ea7cGitHub - kLOsk/adloop: The AI command center for Google Ads, Analytics and Search Console. · GitHub
https://github.com/kLOsk/adloop/Vendor Advisories for CVE-2026-15525(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 3× in last 7d / 3× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-13 04:08 UTCNVD updateCVSS v4 → 2.1
- 2026-07-13 02:43 UTCEG score recompute
- 2026-07-13 02:42 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-918
Frequently asked(4)
What is CVE-2026-15525?
When was CVE-2026-15525 disclosed?
What is the CVSS score of CVE-2026-15525?
How do I remediate CVE-2026-15525?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-15525
Is Your Infrastructure Affected by CVE-2026-15525?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.