CVE-2026-76842

HIGHPre-NVD 8.28.2—
EchelonGraph scoreHIGH confidence

Score 8.2 from GitHub Security Advisory (severity: HIGH) published 2026-08-24. the CNA's CVSS baseline 8.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:vulncheck, epss, ghsa
Trending — 4 sources updated this week
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.2Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 v3
8.2
EG Score
8.2(high)
EG Risk
52(Track)
EG Risk 52/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity82% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
31%
KEV
Not listed

Published

August 24, 2026

Last Modified

August 29, 2026

Advisory Details (4)

Auto-updated Aug 24, 2026
Patch available. Sources: github_pr.
generic

Mercado Pago Node.js SDK through 3.4.0 Path Injection via Unencoded Identifiers in Payment Clients | Advisories | VulnCheck

https://www.vulncheck.com/advisories/mercado-pago-node-js-sdk-through-path-injection-via-unencoded-identifiers-in-payment-clients
github_pr Patch Available

fix: escape dynamic API path parameters

Patch available: mercadopago/sdk-nodejs 3.2.1 (PR #451 merged 2026-07-22)

https://github.com/mercadopago/sdk-nodejs/pull/451
generic

sdk-nodejs/src/clients/payment/get/index.ts at 3.4.0 · mercadopago/sdk-nodejs · GitHub

https://github.com/mercadopago/sdk-nodejs/blob/3.4.0/src/clients/payment/get/index.ts
generic

GitHub - mercadopago/sdk-nodejs: Mercado Pago's Official Node.js SDK · GitHub

https://github.com/mercadopago/sdk-nodejs

Vendor Advisories for CVE-2026-76842(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 27× in last 7d / 27× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-30 01:16 UTCGHSA enrichment
  3. 2026-08-29 12:03 UTCEG score recompute
  4. 2026-08-29 12:03 UTCGHSA enrichment
  5. 2026-08-29 03:57 UTCEG score recompute
  6. 2026-08-29 03:57 UTCGHSA enrichment
  7. 2026-08-28 21:42 UTCEPSS rescore
  8. 2026-08-28 14:46 UTCGHSA enrichment
  9. 2026-08-28 01:30 UTCEG score recompute
  10. 2026-08-28 01:30 UTCGHSA enrichment
  11. 2026-08-27 14:25 UTCEPSS rescore
  12. 2026-08-27 12:19 UTCGHSA enrichment
  13. 2026-08-26 23:08 UTCEG score recompute
  14. 2026-08-26 23:08 UTCGHSA enrichment
  15. 2026-08-26 14:47 UTCEPSS rescore
  16. 2026-08-26 09:56 UTCGHSA enrichment
  17. 2026-08-25 20:45 UTCEG score recompute
  18. 2026-08-25 20:45 UTCGHSA enrichment
  19. 2026-08-25 13:49 UTCEPSS rescore
  20. 2026-08-25 07:34 UTCGHSA enrichment
  21. 2026-08-24 18:23 UTCEG score recompute
  22. 2026-08-24 18:23 UTCGHSA enrichment
  23. 2026-08-24 17:36 UTCEG score recompute
  24. 2026-08-24 17:36 UTCGHSA enrichment
  25. 2026-08-24 14:24 UTCEG score recompute
Show 2 more
  1. 2026-08-24 13:22 UTCEG score recompute
  2. 2026-08-24 13:22 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-76842?
CVE-2026-76842 is a high vulnerability published on August 24, 2026. 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…
When was CVE-2026-76842 disclosed?
CVE-2026-76842 was first published in the National Vulnerability Database on August 24, 2026, with the most recent update on August 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-76842 actively exploited?
CVE-2026-76842 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 69.1% of all scored CVEs.
What is the CVSS score of CVE-2026-76842?
CVE-2026-76842 has a CVSS v4.0 base score of 8.2 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-76842?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-76842, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-76842

Explore →

Is Your Infrastructure Affected by CVE-2026-76842?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs