`check_reserve_proof` counts duplicate entries: one output can inflate `total`

Bug reported by Beni Saprulah was disclosed at August 5, 2026, 10:23 am   |   Business Logic Errors

A vulnerability was discovered in the `check_reserve_proof` function in the Monero wallet software. The vulnerability allowed duplicate entries in the reserve proof, which could artificially inflate the reported total reserve amount without affecting the verification of individual entries. The issue was in the verifier logic, where the accounting was done in a flat manner, adding the output amount for each row without checking for duplicates.

`check_reserve_proof` sums RingCT ECDH amounts without checking the output commitment

Bug reported by Beni Saprulah was disclosed at August 5, 2026, 10:23 am   |   Missing Required Cryptographic Step

The `check_reserve_proof` function in the Monero codebase was found to sum RingCT ECDH amounts without checking the output commitment. The decoded amount was added to the total without verifying that it matched the commitment, which could allow a malicious prover to claim larger reserves than actually exist on-chain.

wallet-rpc crash via malformed /gettransactions response (empty txs → vector::front() in check_tx_key / check_tx_proof)

Bug reported by Beni Saprulah was disclosed at August 5, 2026, 10:23 am   |   NULL Pointer Dereference

A vulnerability was discovered in the Monero wallet software that could cause the wallet-rpc process to crash when handling a malformed response from the daemon's /gettransactions endpoint. The vulnerability was due to the wallet software making assumptions about the response structure that were not always valid, leading to undefined behavior when attempting to access empty data structures. The crash occurred when the wallet software tried to retrieve metadata from the empty response, causing a segmentation fault.

SpendProofV1 txid-substitution: get_spend_proof/check_spend_proof do not verify returned transaction hash

Bug reported by Beni Saprulah was disclosed at August 5, 2026, 10:23 am   |   Missing Required Cryptographic Step

A vulnerability was discovered in the Monero project where the get_spend_proof and check_spend_proof functions do not verify the returned transaction hash against the requested transaction ID. This allows a malicious or compromised daemon to provide a valid serialized transaction body for a different transaction than the one requested, which can be used to create or verify a spend proof for that different transaction.

wallet-rpc describe_transfer uses real_output_in_tx_index instead of real_output: cold-wallet pre-sign review shows wrong ring member

Bug reported by Beni Saprulah was disclosed at August 5, 2026, 10:23 am   |   Array Index Underflow

The wallet-rpc method "describe_transfer" was found to use the wrong index when retrieving information about the ring members for each input. Instead of using the "real_output" index, which represents the position of the real entry in the ring, it used the "real_output_in_tx_index", which represents the position of the output in the source transaction. This resulted in the pre-sign review displaying the wrong information about the ring members to the cold-wallet operator. The signing process itself was not affected, as the correct ring members were used when constructing the transaction. The vulnerability was present in the master branch and the release-v0.18 branch of the monero-project/monero repository.

`relay_tx` wallet-rpc skips `--restricted-rpc` guard and lets any caller corrupt wallet state via attacker-controlled `pending_tx`

Bug reported by Beni Saprulah was disclosed at August 5, 2026, 5:05 am   |   Improper Access Control - Generic

The `relay_tx` wallet-RPC method in Monero was found to bypass the `--restricted-rpc` guard, allowing any caller to corrupt the wallet state by submitting a malicious `pending_tx` blob. The issue was that the `on_relay_tx` handler did not perform any ownership checks on the supplied `pending_tx` before passing it to `commit_tx`, which then updated the wallet state based on the attacker-controlled data. This vulnerability was introduced in the master branch and was present at the time of the commit analyzed.

Unauthenticated Path Traversal (LFI) via /custom-sounds/ when CustomSounds uses FileSystem storage

Bug reported by s was disclosed at August 3, 2026, 1:35 pm   |   Path Traversal

Stored XSS in nameserver field on account settings page

Bug reported by Axolot was disclosed at July 31, 2026, 3:07 pm   |   Cross-site Scripting (XSS) - Stored

A stored XSS vulnerability was discovered in the nameserver field on the account settings page. The lack of input validation and weak CSP configuration allowed the injection of malicious JavaScript code that executed when the settings page was reloaded. The vulnerability was limited to a self-XSS scenario, affecting only the account owner who injected the payload and not other users.

Permission Model bypass: process.report writes (and overwrites) files outside --allow-fs-write paths

Bug reported by Sinan Polat was disclosed at July 30, 2026, 3:07 pm   |   Improper Access Control - Generic

A flaw was found in the Node.js Permission Model enforcement that allowed the process.report function to write (and overwrite) files outside the --allow-fs-write paths.

HTTPS Agent TLS session reuse skips hostname verification across identity policies (incomplete fix of CVE-2026-48934)

Bug reported by vnyuh was disclosed at July 30, 2026, 2:09 am   |   Exploiting Incorrectly Configured SSL/TLS

A vulnerability was identified in Node.js where HTTPS Agent TLS session reuse skipped hostname verification across identity policies, which was an incomplete fix for CVE-2026-48934. This affected Node.js versions 22.x, 24.x, and 26.x.

GitHub scoped user to server tokens can escape their installation

Bug reported by ahacker1 was disclosed at July 29, 2026, 11:35 pm   |   Improper Access Control - Generic

An improper authorization vulnerability in scoped user-to-server (ghu_) token authorization in GitHub Enterprise Server was discovered. The vulnerability allowed an authenticated attacker to access private repositories outside the intended installation scope, which could have included write operations, via an authorization fallback that treated a revoked/deleted installation as a global installation context. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.21 and was fixed in versions 3.20.1, 3.19.5, 3.18.8, 3.17.14, 3.16.17, 3.15.21, and 3.14.26.

Permission Model: --allow-fs-read/--allow-fs-write radix-tree prefix-boundary over-grant

Bug reported by Jiyong Yang was disclosed at July 29, 2026, 11:00 pm   |   Improper Access Control - Generic

A flaw was discovered in the Node.js Permission Model's enforcement of filesystem access control. The vulnerability could allow an attacker granted access to one path to read from or write to paths outside the intended filesystem allowlist, due to issues with the radix-tree prefix-boundary handling. This affected Node.js versions in the main, 22.x, 24.x, and 26.x branches.

`exportReportPdf` mutation shows internal Activity

Bug reported by kimingi was disclosed at July 29, 2026, 3:01 pm   |  

A vulnerability was identified in the PDF export path for disclosed reports. When a report was exported to PDF, the export pipeline did not apply the same visibility and authorization scoping that governs the normal report view. The root cause was that PDF generation assembled report content from the underlying timeline without re-checking each activity against the requester's permission level. The issue was promptly fixed by enforcing the same per-activity visibility checks and disclosure-level scoping along the export path.

HTTPS Agent PFX object-array key collision allows mTLS client identity reuse across different per-request certificates

Bug reported by was disclosed at July 29, 2026, 2:45 pm   |   Improper Authentication - Generic

A flaw in Node.js HTTPS Agent connection reuse was discovered that could cause PFX object-array key collisions, allowing mutual TLS (mTLS) client identities to be reused across requests configured with different client certificates. This vulnerability affected Node.js versions 26.x, 24.x, and 22.x.

Permission Model Bypass: `trace_events.createTracing().enable()` Writes Trace Logs Outside `--allow-fs-write`

Bug reported by Sir bugs was disclosed at July 29, 2026, 2:16 pm   |   Improper Access Control - Generic

A flaw in Node.js Permission Model enforcement was discovered that allowed `trace_events.createTracing().enable()` to write trace logs outside of the `--allow-fs-write` setting. This vulnerability affected Node.js versions 22.x, 24.x, and 26.x.

Unauthenticated SSRF in Voxtelesys integration ('checkUrlForSsrf' Bypass via DNS rebinding)

Bug reported by KT was disclosed at July 29, 2026, 1:48 am   |   Server-Side Request Forgery (SSRF)

An SSRF vulnerability was discovered in Rocket.Chat version 7.13.2 that was caused by a DNS rebinding attack. The vulnerability allowed an attacker to bypass a security check and access internal hosts on the same network as the Rocket.Chat server. The vulnerability was present in the SMS integration feature that used the `checkUrlForSsrf` function, which was bypassed by the DNS rebinding attack.

Sandbox User Can Inject Rogue CA Certificate into OS Trust Store via Sudo-Allowed deploy-certificates.sh

Bug reported by Sergio Garcia was disclosed at July 28, 2026, 3:29 pm   |   Improper Certificate Validation

A vulnerability was found in the Bedrock AgentCore Code Interpreter sandbox. The sandbox granted a user passwordless sudo access to a script that deployed certificates to the OS trust store. An attacker could have generated a rogue CA certificate, placed it in a writable directory, and then used the sudo-allowed script to inject the rogue CA into the trust store. This could have been used to perform man-in-the-middle attacks against TLS connections from the sandbox.

Authentication Bypass via XML Signature Wrapping in SAML SSO

Bug reported by jayden was disclosed at July 27, 2026, 4:37 pm   |   Improper Authentication - Generic

The SAML SSO implementation in Rocket.Chat verified XML signatures but did not bind the validated signature to the `samlp:Response` or `saml:Assertion`. As a result, an attacker could submit a wrapped document carrying forged identity attributes alongside a valid signature made by the trusted IdP certificate, and gain unauthorized access to the system.

GitHub user to server tokens can create issues in any public repository

Bug reported by ahacker1 was disclosed at July 22, 2026, 7:39 pm   |   Improper Access Control - Generic

A vulnerability was identified in GitHub Enterprise Server that allowed a user-to-server token scoped to a GitHub App installation to perform certain write operations on public repositories outside the token's intended scope. The authorization check only verified that the installation had read permissions on the target repository rather than verifying that the token's installation was explicitly granted access to that repository. This vulnerability was fixed by adding a repository scope check for user-to-server tokens issued by global apps.

connect.8x8.com/api/v1: JWT Algorithm Confusion Vulnerability

Bug reported by Kauã Ferreira was disclosed at July 22, 2026, 4:15 am   |   Improper Verification of Cryptographic Signature

A JWT algorithm confusion vulnerability was reported in the `v1` API of `connect.8x8.com`. The JWT verifier did not enforce algorithm pinning and would accept HS256 tokens signed with the RSA public key used as an HMAC secret. The issue was remediated by enforcing RS256 algorithm pinning in the `v1` API verifier.

OAuth redirect uri validation bypass for :proxima_first_party_sync apps

Bug reported by ahacker1 was disclosed at July 21, 2026, 9:43 pm   |   Open Redirect

A vulnerability was identified in GitHub Enterprise Server that allowed an attacker to bypass OAuth redirect URI validation. The vulnerability was fixed in versions 3.20.1, 3.19.5, 3.18.8, 3.17.14, 3.16.17, 3.15.21, and 3.14.26. The vulnerability was reported through the GitHub Bug Bounty program.