CVE-2026-76842
Received Received - Intake

Path Traversal in Mercado Pago Node.js SDK

Vulnerability report for CVE-2026-76842, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-08-24

Last updated on: 2026-08-24

Assigner: VulnCheck

Description

The Mercado Pago Node.js SDK interpolates caller-supplied identifiers into API request paths without percent-encoding them, so characters that are structural in a URL survive into the outgoing request. The payment (get, capture, cancel), paymentRefund (create, total, list, get), advancedPayment (get, capture, cancel, update, updateReleaseDate) and disbursementRefund (create, createAll, listAll) clients build their path as a template literal, for example RestClient.fetch(`/v1/payments/${id}`, ...) in src/clients/payment/get/index.ts. A dot-dot or slash sequence in the identifier is normalised by the WHATWG URL parser and redirects the request to a different endpoint, and a question mark appends attacker-chosen query parameters, in both cases carrying the merchant's own access token. An application that forwards an identifier influenced by an untrusted party into one of these methods without an ownership check therefore allows that party to reach other resources within the merchant's token scope. The repository already contains the intended helper, encodePathParam in src/utils/path.ts, which pull request 451 applied to roughly 29 other clients while leaving these unchanged.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-24
Last Modified
2026-08-24
Generated
2026-08-24
AI Q&A
2026-08-24
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 3 associated CPEs
Vendor Product Version / Range
mercado_pago node_js_sdk *
mercadopago sdk-nodejs 3.4.0
mercadopago sdk-nodejs to 3.4.0 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-22 The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

The Mercado Pago Node.js SDK has a flaw where it inserts user-provided identifiers directly into API request paths without proper URL encoding. This allows characters like dots, slashes, or question marks in these identifiers to change the intended API endpoint or add malicious query parameters. The vulnerability affects payment, paymentRefund, advancedPayment, and disbursementRefund clients that use template literals for path construction.

Detection Guidance

Check if your application uses Mercado Pago Node.js SDK version 3.4.0 or earlier. Review code for template literals in payment, paymentRefund, advancedPayment, or disbursementRefund clients that interpolate user-supplied identifiers without encoding. Use static analysis tools to detect unencoded path parameters in API requests.

Impact Analysis

An attacker could manipulate identifiers to redirect requests to unauthorized resources within the merchant's token scope. This could lead to unauthorized access to payment data, refund operations, or other sensitive actions controlled by the merchant's access token.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive payment data, violating GDPR's data protection principles and HIPAA's requirements for safeguarding protected health information. It may result in non-compliance due to potential data breaches and unauthorized data exposure.

Mitigation Strategies

Upgrade to the latest SDK version where path-parameter encoding is applied. Use the encodePathParam helper for all dynamic path segments. Validate and sanitize all user-supplied identifiers before passing them to SDK methods. Implement strict input validation to reject identifiers containing special characters like dots, slashes, or question marks.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-76842. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart