Vulnerability in github.com/monetr/monetr (CVE-2026-41644)
Summary
Vulnerability in github.com/monetr/monetr (CVE-2026-41644). Confidential information can be exposed externally. Exploitable via POST /api/lunch_flow/link. Mitigation: upgrade to 1.12.5 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-41644 has been found in github.com/monetr/monetr.
Attackers can target a specific entry point like POST /api/lunch_flow/link over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.1/10.
What to do: upgrade github.com/monetr/monetr to 1.12.5 or later.
If unsure, ask your IT team or search "github.com/monetr/monetr CVE-2026-41644" on the vendor's site.
CVE-2026-41644 (github.com/monetr/monetr) — CWE-209 / CVSS v3 7.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /api/lunch_flow/link / io.ReadAll / error / my.monetr.app
Patched: 1.12.5 — apply immediately
Workaround: set lunchFlow.enabled: false
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-209) exists in github.com/monetr/monetr. Attackers reach the vulnerable code path via POST /api/lunch_flow/link.
Check the vendor advisory for the affected versions of github.com/monetr/monetr. Attack surface: POST /api/lunch_flow/link / io.ReadAll / error / my.monetr.app.
Severity: High (CVSS 7.1/10). Confidential information can be exposed externally.
Update to 1.12.5.
Workaround: set lunchFlow.enabled: false
Search webserver/proxy logs for unusual POST /api/lunch_flow/link requests with malformed payloads or SQL meta-characters. Run grep -r 'github.com/monetr/monetr' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/monetr/monetr' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/monetr/monetrを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /api/lunch_flow/link' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/lunch_flow/linkへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply temporary workaround mitigate
set lunchFlow.enabled: falseパッチが適用されるまでの応急処置として、set lunchFlow.enabled: false を実施。回避策の副作用 (機能低下) を確認した上で。
-
4Apply patch patch
Upgrade github.com/monetr/monetr to 1.12.5ステージング環境で 1.12.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
5Post-deployment verification verify
Replay attack against POST /api/lunch_flow/link on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- web github.com
- web github.com