# CVE-2020-37095: Cyberoam Authentication Client 2.1.2.7 - Buffer Overflow (SEH)

> Remote attackers can execute arbitrary code with system-level access via a buffer overflow in the Cyberoam Authentication Client.

- **Severity:** High 8.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 6 Feb 2026
- **Updated:** 5 Mar 2026
- **Also known as:** GHSA-3rq8-jjh5-j8v3

## What is CVE-2020-37095?

CVE-2020-37095 is a high-severity memory corruption vulnerability in Cyberoam Authentication Client, published on 6 Feb 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Cyberoam Authentication Client 2.1.2.7 contains a buffer overflow vulnerability that allows remote attackers to execute arbitrary code by overwriting Structured Exception Handler (SEH) memory. Attackers can craft a malicious input in the 'Cyberoam Server Address' field to trigger a bind TCP shell on port 1337 with system-level access.

Weakness: CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2020-37095?


## How do I fix CVE-2020-37095?

No fix has been published for CVE-2020-37095 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-37095 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-37095 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-37095 and fix it if it is affected.

What it is: CVE-2020-37095 is a high-severity memory corruption vulnerability in Cyberoam Authentication Client, published on 6 Feb 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-37095 exists.

Affected product: Cyberoam Authentication Client. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-37095/ (Markdown: https://insights.sbomify.com/CVE-2020-37095/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-37095
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-37095
- OSV: https://osv.dev/vulnerability/CVE-2020-37095

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-37095/
Summaries are generated and may contain mistakes; the official description above is the record.