CVE-2026-76842

HIGHPre-NVD 8.28.2
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 8.2 from GitHub Security Advisory (severity: HIGH) published 2026-08-24. A secondary CVSS source baseline 8.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week
8.2EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.2Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.2HIGHmedium confidence
EG Risk
52
EG Risk 52/100

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 (value × EchelonGraph’s weight)
Severity82% × 45%
The EG Score, 8.2 of 10.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
40th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 24, 2026

Last Modified

October 14, 2026

Advisory Details (4)

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

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 pull request 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
Web page

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
Web page

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 22× in last 7d / 100× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 180 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 80 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  2. 2026-10-14 13:32 UTCEG score recompute
  3. 2026-10-14 13:32 UTCGHSA enrichmentGHSA-8vxq-h2gr-x277 · GitHub severity HIGH · GitHub CVSS 8.2
  4. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  5. 2026-10-13 07:03 UTCEG score recompute
  6. 2026-10-13 07:03 UTCGHSA enrichmentGHSA-8vxq-h2gr-x277 · GitHub severity HIGH · GitHub CVSS 8.2
  7. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  8. 2026-10-12 15:38 UTCEG score recompute
  9. 2026-10-11 19:23 UTCEG score recompute
  10. 2026-10-11 16:39 UTCEG score recompute
  11. 2026-10-11 13:58 UTCEG score recompute
  12. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  13. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  14. 2026-10-10 13:06 UTCEG score recompute
  15. 2026-10-10 13:05 UTCGHSA enrichmentGHSA-8vxq-h2gr-x277 · GitHub severity HIGH · GitHub CVSS 8.2
  16. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  17. 2026-10-09 04:58 UTCEG score recompute
  18. 2026-10-09 04:58 UTCGHSA enrichmentGHSA-8vxq-h2gr-x277 · GitHub severity HIGH · GitHub CVSS 8.2
  19. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  20. 2026-10-08 04:03 UTCEG score recompute
  21. 2026-10-08 04:02 UTCGHSA enrichmentGHSA-8vxq-h2gr-x277 · GitHub severity HIGH · GitHub CVSS 8.2
  22. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  23. 2026-10-07 05:52 UTCGHSA enrichmentGHSA-8vxq-h2gr-x277 · GitHub severity HIGH · GitHub CVSS 8.2
  24. 2026-10-06 16:40 UTCEG score recompute
  25. 2026-10-06 16:40 UTCGHSA enrichmentGHSA-8vxq-h2gr-x277 · GitHub severity HIGH · GitHub CVSS 8.2
Show 75 more
  1. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  2. 2026-10-06 02:53 UTCEG score recompute
  3. 2026-10-06 02:53 UTCGHSA enrichmentGHSA-8vxq-h2gr-x277 · GitHub severity HIGH · GitHub CVSS 8.2
  4. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  5. 2026-10-05 09:55 UTCEG score recompute
  6. 2026-10-05 09:55 UTCGHSA enrichmentGHSA-8vxq-h2gr-x277 · GitHub severity HIGH · GitHub CVSS 8.2
  7. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  8. 2026-10-04 20:43 UTCGHSA enrichmentGHSA-8vxq-h2gr-x277 · GitHub severity HIGH · GitHub CVSS 8.2
  9. 2026-10-04 05:44 UTCGHSA enrichmentGHSA-8vxq-h2gr-x277 · GitHub severity HIGH · GitHub CVSS 8.2
  10. 2026-10-03 16:33 UTCEG score recompute
  11. 2026-10-03 16:33 UTCGHSA enrichmentGHSA-8vxq-h2gr-x277 · GitHub severity HIGH · GitHub CVSS 8.2
  12. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  13. 2026-10-03 02:07 UTCEG score recompute
  14. 2026-10-03 02:07 UTCGHSA enrichmentGHSA-8vxq-h2gr-x277 · GitHub severity HIGH · GitHub CVSS 8.2
  15. 2026-10-02 12:54 UTCGHSA enrichmentGHSA-8vxq-h2gr-x277 · GitHub severity HIGH · GitHub CVSS 8.2
  16. 2026-10-01 22:50 UTCEG score recompute
  17. 2026-10-01 22:50 UTCGHSA enrichmentGHSA-8vxq-h2gr-x277 · GitHub severity HIGH · GitHub CVSS 8.2
  18. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  19. 2026-10-01 09:39 UTCGHSA enrichmentGHSA-8vxq-h2gr-x277 · GitHub severity HIGH · GitHub CVSS 8.2
  20. 2026-09-30 20:28 UTCEG score recompute
  21. 2026-09-30 20:28 UTCGHSA enrichmentGHSA-8vxq-h2gr-x277 · GitHub severity HIGH · GitHub CVSS 8.2
  22. 2026-09-30 07:15 UTCEG score recompute
  23. 2026-09-30 07:15 UTCGHSA enrichmentGHSA-8vxq-h2gr-x277 · GitHub severity HIGH · GitHub CVSS 8.2
  24. 2026-09-29 15:24 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  25. 2026-09-29 15:15 UTCGHSA enrichmentGHSA-8vxq-h2gr-x277 · GitHub severity HIGH · GitHub CVSS 8.2
  26. 2026-09-28 21:33 UTCEG score recompute
  27. 2026-09-28 21:33 UTCGHSA enrichmentGHSA-8vxq-h2gr-x277 · GitHub severity HIGH · GitHub CVSS 8.2
  28. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  29. 2026-09-28 03:46 UTCGHSA enrichmentGHSA-8vxq-h2gr-x277 · GitHub severity HIGH · GitHub CVSS 8.2
  30. 2026-09-27 14:33 UTCEG score recompute
  31. 2026-09-27 14:33 UTCGHSA enrichmentGHSA-8vxq-h2gr-x277 · GitHub severity HIGH · GitHub CVSS 8.2
  32. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  33. 2026-09-27 00:41 UTCEG score recompute
  34. 2026-09-27 00:41 UTCGHSA enrichmentGHSA-8vxq-h2gr-x277 · GitHub severity HIGH · GitHub CVSS 8.2
  35. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  36. 2026-09-26 00:28 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  37. 2026-09-25 11:47 UTCGHSA enrichmentGHSA-8vxq-h2gr-x277 · GitHub severity HIGH · GitHub CVSS 8.2
  38. 2026-09-24 21:20 UTCEG score recompute
  39. 2026-09-24 21:20 UTCGHSA enrichmentGHSA-8vxq-h2gr-x277 · GitHub severity HIGH · GitHub CVSS 8.2
  40. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  41. 2026-09-24 12:47 UTCGHSA enrichmentGHSA-8vxq-h2gr-x277 · GitHub severity HIGH · GitHub CVSS 8.2
  42. 2026-09-23 23:35 UTCEG score recompute
  43. 2026-09-23 23:35 UTCGHSA enrichmentGHSA-8vxq-h2gr-x277 · GitHub severity HIGH · GitHub CVSS 8.2
  44. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  45. 2026-09-23 10:24 UTCGHSA enrichmentGHSA-8vxq-h2gr-x277 · GitHub severity HIGH · GitHub CVSS 8.2
  46. 2026-09-22 21:13 UTCEG score recompute
  47. 2026-09-22 21:13 UTCGHSA enrichmentGHSA-8vxq-h2gr-x277 · GitHub severity HIGH · GitHub CVSS 8.2
  48. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  49. 2026-09-22 08:02 UTCEG score recompute
  50. 2026-09-22 08:01 UTCGHSA enrichmentGHSA-8vxq-h2gr-x277 · GitHub severity HIGH · GitHub CVSS 8.2
  51. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  52. 2026-09-21 18:50 UTCGHSA enrichmentGHSA-8vxq-h2gr-x277 · GitHub severity HIGH · GitHub CVSS 8.2
  53. 2026-09-21 05:39 UTCEG score recompute
  54. 2026-09-21 05:39 UTCGHSA enrichmentGHSA-8vxq-h2gr-x277 · GitHub severity HIGH · GitHub CVSS 8.2
  55. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  56. 2026-09-20 16:01 UTCGHSA enrichmentGHSA-8vxq-h2gr-x277 · GitHub severity HIGH · GitHub CVSS 8.2
  57. 2026-09-20 02:48 UTCEG score recompute
  58. 2026-09-20 02:48 UTCGHSA enrichmentGHSA-8vxq-h2gr-x277 · GitHub severity HIGH · GitHub CVSS 8.2
  59. 2026-09-19 13:36 UTCGHSA enrichmentGHSA-8vxq-h2gr-x277 · GitHub severity HIGH · GitHub CVSS 8.2
  60. 2026-09-19 00:24 UTCEG score recompute
  61. 2026-09-19 00:24 UTCGHSA enrichmentGHSA-8vxq-h2gr-x277 · GitHub severity HIGH · GitHub CVSS 8.2
  62. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  63. 2026-09-18 11:13 UTCGHSA enrichmentGHSA-8vxq-h2gr-x277 · GitHub severity HIGH · GitHub CVSS 8.2
  64. 2026-09-17 22:01 UTCEG score recompute
  65. 2026-09-17 22:01 UTCGHSA enrichmentGHSA-8vxq-h2gr-x277 · GitHub severity HIGH · GitHub CVSS 8.2
  66. 2026-09-17 08:50 UTCGHSA enrichmentGHSA-8vxq-h2gr-x277 · GitHub severity HIGH · GitHub CVSS 8.2
  67. 2026-09-16 19:38 UTCEG score recompute
  68. 2026-09-16 19:38 UTCGHSA enrichmentGHSA-8vxq-h2gr-x277 · GitHub severity HIGH · GitHub CVSS 8.2
  69. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  70. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  71. 2026-09-16 05:01 UTCGHSA enrichmentGHSA-8vxq-h2gr-x277 · GitHub severity HIGH · GitHub CVSS 8.2
  72. 2026-09-15 15:50 UTCEG score recompute
  73. 2026-09-15 15:50 UTCGHSA enrichmentGHSA-8vxq-h2gr-x277 · GitHub severity HIGH · GitHub CVSS 8.2
  74. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  75. 2026-09-15 02:37 UTCGHSA enrichmentGHSA-8vxq-h2gr-x277 · GitHub severity HIGH · GitHub CVSS 8.2

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-76842?
CVE-2026-76842 is a high-severity vulnerability; its CVE record was 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 made public?
CVE-2026-76842 was made public on August 3, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 24, 2026. EchelonGraph's copy of the record carries a last-modified date of October 14, 2026; the record at its source may have been updated since.
Is CVE-2026-76842 actively exploited?
CVE-2026-76842 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (40th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-76842?
CVE-2026-76842 has a CVSS base score of 8.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-76842?
A fix for CVE-2026-76842 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-76842 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs