CVE-2026-39901: monetr Protected Transactions Deletable Vulnerability

MODERATE
Advisory Identifier: GHSA-hqxq-hwqf-wg83
CVSS 5.7
CWE-285
Published
Advisory Summary

CVE-2026-39901 is a MODERATE (CVSS 5.7) protected transactions deletable vulnerability (CWE-285: Improper Authorization) affecting monetr libraries in the Go ecosystem. The issue involves protected transactions deletable via put. Remediation is available by upgrading affected packages to version 1.12.3.

CVE-2026-39901 at a Glance

CVE Identifier CVE-2026-39901
GHSA Identifier GHSA-hqxq-hwqf-wg83
Severity MODERATE
CVSS v3.1 Base Score 5.7
CWE Classification CWE-285: Improper Authorization
Affected Product monetr
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 5.7

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2026-39901

To remediate this vulnerability, upgrade all affected monetr dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/monetr/monetr fixed: 1.12.3
Upgrade github.com/monetr/monetr to 1.12.3
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/monetr/monetr

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-39901, inspect your project dependencies for monetr:

inspect dependencies for github.com/monetr/monetr

Analyze the terminal output to locate any version of monetr in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.12.3), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-285: Improper Authorization, where the product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. In monetr, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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 on the same synced transaction showed: - `DELETE` was denied with the expected protection error for non-manual links - `PUT` with a user-supplied `deletedAt` value succeeded and returned `200 OK` - a subsequent transaction list no longer showed the transaction - `GET` by transaction ID still returned the record with `deletedAt` populated This demonstrates a policy bypass: although the server explicitly defines synced transactions on non-manual links as non-deletable through the dedicated delete route, the same outcome can still be achieved through the update route by setting the soft-delete field directly. The vulnerability is therefore not a simple UI inconsistency. It is a server-side authorization and integrity flaw caused by trusting a client-supplied full transaction object and failing to protect sensitive server-managed fields from modification. ### PoC The issue can be reproduced by identifying a synced transaction on a non-manual link, confirming that the normal `DELETE` route rejects deletion, then submitting an update request that sets the transaction’s `deletedAt` field. The transaction will then disappear from normal listing views even though direct retrieval still shows the record as soft-deleted. ### Impact - **Type:** Authorization bypass / integrity violation - **Who is impacted:** Authenticated tenant users and any deployment relying on synced transaction immutability for non-manual links - **Security impact:** Attackers can hide or effectively delete protected imported transactions that should not be deletable, compromising transaction history, bookkeeping integrity, and trust in audit-relevant server-managed fields - **Attack preconditions:** The attacker must be authenticated and able to access a synced transaction within their own tenant/account scope

CVE-2026-39901 Affected monetr Versions

1 component(s)
Fixed Versions:
1.12.3
Product / Package Ecosystem Affected Versions Fixed Version
github.com/monetr/monetr
Go
< 1.12.3
1.12.3

References

Frequently Asked Questions

What is CVE-2026-39901?
CVE-2026-39901 is a security vulnerability in monetr involving Protected Transactions Deletable via PUT under CWE-285: Improper Authorization.
Which monetr versions are affected?
Affected versions include releases prior to 1.12.3 across affected packages: github.com/monetr/monetr.
What version fixes CVE-2026-39901?
Upgrading to 1.12.3 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/monetr/monetr affected?
Yes, github.com/monetr/monetr is affected in releases prior to 1.12.3. Upgrade your dependency to 1.12.3 or later.
What is the CVSS score of CVE-2026-39901?
CVE-2026-39901 has a CVSS v3.1 base score of 5.7 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:N.
What CWE is associated with CVE-2026-39901?
CVE-2026-39901 is classified under CWE-285: Improper Authorization (The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.).
How can I check Go dependencies for CVE-2026-39901?
Run the dependency tree command: 'inspect dependencies for github.com/monetr/monetr'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-hqxq-hwqf-wg83",
  "modified" : "2026-07-21T14:53:20Z",
  "published" : "2026-04-08T19:23:00Z",
  "aliases" : [ "CVE-2026-39901" ],
  "summary" : "monetr: Protected Transactions Deletable via PUT",
  "details" : "### Summary\nA 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.\n\n### Details\nThe 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.\n\nHowever, 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.\n\nVerified behavior on the same synced transaction showed:\n\n- `DELETE` was denied with the expected protection error for non-manual links\n- `PUT` with a user-supplied `deletedAt` value succeeded and returned `200 OK`\n- a subsequent transaction list no longer showed the transaction\n- `GET` by transaction ID still returned the record with `deletedAt` populated\n\nThis demonstrates a policy bypass: although the server explicitly defines synced transactions on non-manual links as non-deletable through the dedicated delete route, the same outcome can still be achieved through the update route by setting the soft-delete field directly.\n\nThe vulnerability is therefore not a simple UI inconsistency. It is a server-side authorization and integrity flaw caused by trusting a client-supplied full transaction object and failing to protect sensitive server-managed fields from modification.\n\n### PoC\nThe issue can be reproduced by identifying a synced transaction on a non-manual link, confirming that the normal `DELETE` route rejects deletion, then submitting an update request that sets the transaction’s `deletedAt` field. The transaction will then disappear from normal listing views even though direct retrieval still shows the record as soft-deleted.\n\n### Impact\n- **Type:** Authorization bypass / integrity violation\n- **Who is impacted:** Authenticated tenant users and any deployment relying on synced transaction immutability for non-manual links\n- **Security impact:** Attackers can hide or effectively delete protected imported transactions that should not be deletable, compromising transaction history, bookkeeping integrity, and trust in audit-relevant server-managed fields\n- **Attack preconditions:** The attacker must be authenticated and able to access a synced transaction within their own tenant/account scope",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/monetr/monetr"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.12.3"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.12.2"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/monetr/monetr/security/advisories/GHSA-hqxq-hwqf-wg83"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-39901"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/monetr/monetr"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/monetr/monetr/releases/tag/v1.12.3"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-285" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-04-08T19:23:00Z",
    "nvd_published_at" : "2026-04-08T22:16:22Z"
  }
}