# CVE-2026-41195: mosparo: Rule package source URL stored SSRF enables internal HTTP probing

> An editor can store a malicious URL in rule package settings, causing the server to fetch it and enabling internal network probing.

- **Severity:** Medium 5.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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:** 12 May 2026
- **Updated:** 18 May 2026
- **Also known as:** GHSA-92fh-26qf-r8rg

## What is CVE-2026-41195?

CVE-2026-41195 is a medium-severity server-side request forgery vulnerability in mosparo, published on 12 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

mosparo is the modern solution to protect your online forms from spam. Prior to 1.4.13, the automatic rule package source URL feature allows a project member with the editor role to store an attacker-controlled URL that the server later fetches. Because the server follows http/https redirects and does not restrict private or loopback destinations, this becomes a stored SSRF primitive that can be turned into an internal HTTP probing oracle. This vulnerability is fixed in 1.4.13.

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

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


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

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

## Is CVE-2026-41195 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-41195 is a medium-severity server-side request forgery vulnerability in mosparo, published on 12 May 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-41195 exists.

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

## Sources

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

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