# CVE-2026-41644: monetr is vulnerable to server-side request forgery in Lunch Flow link creation and refresh

> Authenticated users can force the monetr server to make arbitrary HTTP requests and read response bodies, potentially exposing internal network resources.

- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:L/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 May 2026
- **Updated:** 7 May 2026
- **Also known as:** GHSA-29v9-frvh-c426, GO-2026-4966

## What is CVE-2026-41644?

CVE-2026-41644 is a high-severity server-side request forgery vulnerability in monetr, published on 7 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

monetr is a budgeting application for recurring expenses. Prior to version 1.12.5, a server-side request forgery (SSRF) vulnerability in monetr's Lunch Flow integration allowed any authenticated user on a self-hosted instance to cause the monetr server to issue HTTP GET requests to arbitrary URLs supplied by the caller, with the response body from non-200 upstream responses reflected back in the API error message. This issue has been patched in version 1.12.5.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-770 (Allocation of Resources Without Limits or Throttling), CWE-209 (Generation of Error Message Containing Sensitive Information)

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

3 open source packages ship an affected version, including github.com/monetr/monetr. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/monetr/monetr` | Go | All versions | 1.12.5 |
| `github.com/monetr/monetr` | Go | All versions | 1.12.5 |
| `github.com/monetr/monetr` | Go | All versions | 1.12.5 |

Products: Monetr Monetr.

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

Upgrade github.com/monetr/monetr to 1.12.5 or later.

## Is CVE-2026-41644 being exploited?

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

## Other vulnerabilities in monetr

- [CVE-2026-40481](https://insights.sbomify.com/CVE-2026-40481/): monetr: Unauthenticated Stripe webhook reads attacker-sized request bodies before signature validation (high 8.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-41644 is a high-severity server-side request forgery vulnerability in monetr, published on 7 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-41644 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/monetr/monetr (Go): affected all versions; fixed in 1.12.5
- github.com/monetr/monetr (Go): affected all versions; fixed in 1.12.5
- github.com/monetr/monetr (Go): affected all versions; fixed in 1.12.5

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

## Sources

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

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