monetr: Protected Transactions Deletable via PUT

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.7 · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:N

EPSS

• CVE-2026-39901: 0.29% estimated exploitation activity in the next 30 days; percentile 21.88 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary A transaction integrity flaw allows an authenticated tenant user to soft-delete synced non-manual transactions through the transaction update endpoint, despite the application explicitly blocking deletion of those transactions via the normal DELETE path. This bypass undermines the intended protection for imported transaction records and allows protected transactions to be hidden from normal views. Details The issue affects the transaction update path for synced transactions associated with non-manual links. The intended policy is clearly enforced in the DELETE handler: deletion of synced transactions for non-manual links is rejected with an error indicating that such transactions cannot be deleted. However, the PUT update path still accepts a client-controlled full Transaction object and persists fields that should be server-managed, including deletedAt. The update logic appears to restrict only selected fields, which leaves deletedAt attacker-controllable. Verified behavior…

Published by the source

8 Apr 2026, 19:23 UTC

Last modified by the source

10 Apr 2026, 15:00 UTC

Source last checked

26 Oct 2026, 15:19 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-hqxq-hwqf-wg83

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-39901

Advisory: monetr: Protected Transactions Deletable via PUT
IDs: CVE-2026-39901, GHSA-hqxq-hwqf-wg83
Record: https://patchnext.com/advisories/cve-2026-39901 (revision 1, source checked 26 Oct 2026, 15:19 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/monetr/monetr 1.12.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/monetr/monetr: affected <= 1.12.2; fixed in 1.12.3

## Suggested inspection (read-only)
- Go github.com/monetr/monetr: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/monetr/monetr.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-hqxq-hwqf-wg83 (GitHub-reviewed advisory GHSA-hqxq-hwqf-wg83 lists affected ranges: Go github.com/monetr/monetr >=0 <=1.12.2)

Commands are suggestions: review each one before running it.