Skip to content
Applications

CVE-2020-36997

8.4
High
EPSS 0.41%

Buffer overflow in BacklinkSpeed 2.4 enables SEH chain corruption via crafted file import.

exploited
Public proof of concept per CISA SSVC; not in CISA KEV
fix
No fixed release stated by the publisher
likelihood
EPSS 0.41%top 65% of scored CVEs
Published 29 Jan 2026Analysed here 30 Jan 2026CVSS scored by the publisher (CNA)
common questions

Is CVE-2020-36997 being exploited?

Not confirmed. CVE-2020-36997 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.41% probability of exploitation in the next 30 days.

How severe is CVE-2020-36997?

CVE-2020-36997 is rated High with a CVSS score of 8.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2020-36997?

Not known from our data. No patch reference has been recorded for CVE-2020-36997, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2020-36997 affect?

CVE-2020-36997 affects BacklinkSpeed 2.4. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2020-36997?

Patch when available; restrict and validate file imports.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
BacklinkSpeed 2.4
impact

Arbitrary code execution via SEH overwrite from a crafted import file, potentially gaining control of the application.

action required

Patch when possible

affected versions
Dummysoftware BacklinkSpeed
  • affected2.4

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

cisa ssvc

exploitation
poc
automatable
yes
technical impact
total

Assessed by CISA 29 Jan 2026 (SSVC 2.0.3).

timeline

  1. 29 Jan 2026Published
  2. 29 Jan 2026CISA SSVC assessment: exploitation poc · same day later
  3. 30 Jan 2026Analysed by vulneraibility.com · same day later
  4. 12 May 2026CVE record last updated · 103 days (about 3 months) later
how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
4 references in the CVE record: 1 advisory, 1 exploit, 2 links

sources

  • CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
  • NVD: CVSS and CPE data
  • CISA Vulnrichment (ADP): SSVC decision points
  • FIRST EPSS: exploit probability and percentile
  • Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved