CVE-2026-62362

MEDIUMPre-NVD 4.94.9
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 4.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (27th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-102944 (ENISA EUVD)Source: ENISA EUVD

4.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 4.9Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

PeerBanHelper automatically blocks unwanted, leeching, and abnormal BitTorrent peers using customizable and cloud rules. From 5.0.0 until 9.3.15, the /api/statistic/analysis/field endpoint accepts a crafted field query parameter from an authenticated user and passes it to countField or sumField. The mapField() method forwards unrecognized field names without sanitization, so unrecognized field names are interpolated into SQL through ${field} across the SQLite, MySQL, and PostgreSQL mappers. Successful exploitation can read all data in the PeerBanHelper database. This issue is fixed in version 9.3.15.

CVSS v3
4.9
EG Score
4.9MEDIUMmedium confidence
EG Risk
38
EG Risk 38/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity49% × 45%
Impact severity (EG Severity): CVSS 4.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
0.3%
EPSS %ILE
27th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (4.9): severity, escalated by confirmed exploitation. This CVE's 4.9 is its impact severity (EG Severity), not escalated.

EG Severity
4.9 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

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

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (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

October 16, 2026

Last Modified

October 28, 2026

Advisory Details (3)

Auto-updated Oct 16, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

SQL injection via ${field} interpolation in MyBatis mapper for analysis endpoint · Advisory · PBH-BTN/PeerBanHelper · GitHub

https://github.com/PBH-BTN/PeerBanHelper/security/advisories/GHSA-pc89-mfwm-hj9x
GitHub release Patch Available

v9.3.15

Patch available: PBH-BTN/PeerBanHelper v9.3.15

https://github.com/PBH-BTN/PeerBanHelper/releases/tag/v9.3.15
GitHub commit

commit bec34c8b93c6 (PBH-BTN/PeerBanHelper)

Fix landed in PBH-BTN/PeerBanHelper commit bec34c8b93c6 — awaiting tagged release

https://github.com/PBH-BTN/PeerBanHelper/commit/bec34c8b93c6ea3a3bc2ad992aedd41b95cd400a

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 22× 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.

  1. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  2. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  3. 2026-10-28 19:28 UTCEG score recompute
  4. 2026-10-28 18:29 UTCEG score recompute
  5. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  6. 2026-10-28 02:55 UTCOSV refresh
  7. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  8. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  9. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  10. 2026-10-25 14:14 UTCEG score recompute
  11. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  12. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  13. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  14. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  15. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  16. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  17. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  18. 2026-10-18 03:24 UTCEG score recompute
  19. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  20. 2026-10-16 18:16 UTCEG score recompute
  21. 2026-10-16 16:50 UTCEG score recomputeFirst assessed: 4.9 MEDIUM
  22. 2026-10-16 16:47 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-62362?
CVE-2026-62362 is a medium-severity vulnerability; its CVE record was published on October 16, 2026. PeerBanHelper automatically blocks unwanted, leeching, and abnormal BitTorrent peers using customizable and cloud rules. From 5.0.0 until 9.3.15, the /api/statistic/analysis/field endpoint accepts a crafted field query parameter from an authenticated user and passes it to countField or sumField.…
When was the CVE record for CVE-2026-62362 published?
The CVE record for CVE-2026-62362 was published on October 16, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 28, 2026; the record at its source may have been updated since.
Is CVE-2026-62362 actively exploited?
CVE-2026-62362 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (27th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-62362?
CVE-2026-62362 has a CVSS base score of 4.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-62362?
A fix for CVE-2026-62362 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-62362?

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

Book a Demo →Browse All CVEs