CVE-2026-41644: monetr is vulnerable to server-side request forgery in Lunch Flow link creation and refresh
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-01 19:19 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
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.
Description quoted from the CVE record (assigned by GitHub_M, published 2026-05-07).
Weakness: CWE-209: Generation of Error Message Containing Sensitive Information; CWE-770: Allocation of Resources Without Limits or Throttling; CWE-918: Server-Side Request Forgery (SSRF)
How it can be exploited
Exploitable over the network with low attack complexity with no special attack requirements needing low privileges and no user interaction. Impact: confidentiality high, integrity none, availability low. 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
CISA assessment (SSVC): CISA has no evidence of exploitation. Automatable: yes. Technical impact: partial.
Public exploit evidence (Exploit Observer)
Also known as: EUVD-2026-28353, GHSA-29v9-frvh-c426
VEDAS cluster: VEDAS:CROWSNEST
Exploit Observer links 3 pieces of public exploit code or detection modules that name this CVE or one of its aliases.
Exploit code and modules (3)
Code that names this CVE. A repository can be a working exploit, a scanner, a fake or malware; read it before running anything.
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/suricata/2026/CVE-2026-41644.rules
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/suricata/2026/CVE-2026-41644.rules
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/suricata/2026/CVE-2026-41644.rules
Vulnerability databases and vendor advisories (6)
Catalogue entries, not exploit evidence.
- Vulnerability database or vendor advisory: https://euvd.enisa.europa.eu/enisa/EUVD-2026-28353
- Vulnerability database or vendor advisory: https://github.com/advisories/GHSA-29v9-frvh-c426
- Vulnerability database or vendor advisory: https://nvd.nist.gov/vuln/detail/CVE-2026-41644
- Vulnerability database or vendor advisory: https://osv.dev/vulnerability/CVE-2026-41644
- Vulnerability database or vendor advisory: https://osv.dev/vulnerability/GHSA-29v9-frvh-c426
- Vulnerability database or vendor advisory: https://www.suse.com/security/cve/CVE-2026-41644
4 more references returned by Exploit Observer did not name this CVE or an alias, so they are left out.
VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.
Live scores
- EPSS
- 0.003
low predicted chance of attack - VEDAS
- 0.974
strong exploit evidence - On CISA KEV
- Not listed
- Detection rule
- Suricata
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| monetr monetr | version < 1.12.5 | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
Exploit Observer also maps it to: go github.com/monetr/monetr, monetr monetr.
How to fix it
No fixed version or vendor advisory is listed in the CVE record yet. Watch the vendor’s security page.
How to detect it
Suricata rules (network detection)
1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-41644 monetr - Server-Side Request Forgery via Lunch Flow integration apiUrl to internal host. Add them to your Suricata rule set and reload.
Show the rules
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-41644 monetr - Server-Side Request Forgery via Lunch Flow integration apiUrl to internal host"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"/api/lunch_flow"; nocase; fast_pattern; http.request_body; pcre:"/https?(?:\x3a|%3a)(?:\x2f\x2f|%2f%2f)(?:127\.|0\.0\.0\.0|localhost|169\.254\.169\.254|metadata|10\.|192\.168\.|172\.(?:1[6-9]|2[0-9]|3[01])\.|\x5b|%5b)/i"; classtype:web-application-attack; reference:cve,CVE-2026-41644; reference:url,https://www.exploit.observer/?keyword=CVE-2026-41644&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=monetr&match=exact; sid:1096006; rev:1;)
CVE-2026-41644.rules on GitHub
References
Other references
- https://github.com/monetr/monetr/security/advisories/GHSA-29v9-frvh-c426 (x_refsource_CONFIRM)
- https://github.com/monetr/monetr/pull/3122 (x_refsource_MISC)
- https://github.com/monetr/monetr/commit/c260caa3c573a4a396ec2d264c7641a5d958385b (x_refsource_MISC)
- https://github.com/monetr/monetr/releases/tag/v1.12.5 (x_refsource_MISC)
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.