# CVE-2020-26118: Deserialization in n/a

> An authenticated attacker can execute arbitrary commands on the system by submitting a malicious serialized Java object to the Collaborator Server.

- **Severity:** High 8.8 (`CVSS:3.1/AC:L/AV:N/A:H/C:H/I:H/PR:L/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jan 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-qqc4-654m-g55g

## What is CVE-2020-26118?

CVE-2020-26118 is a high-severity unsafe deserialization vulnerability in n/a, published on 11 Jan 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In SmartBear Collaborator Server through 13.3.13302, use of the Google Web Toolkit (GWT) API introduces a post-authentication Java deserialization vulnerability. The application's UpdateMemento class accepts a serialized Java object directly from the user without properly sanitizing it. A malicious object can be submitted to the server via an authenticated attacker to execute commands on the underlying system.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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

It affects 1 product.


Products: Smartbear Collaborator.

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

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

## Is CVE-2020-26118 being exploited?

There is no known exploitation of CVE-2020-26118 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2021-41657](https://insights.sbomify.com/CVE-2021-41657/): Cross-site request forgery in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-26118 is a high-severity unsafe deserialization vulnerability in n/a, published on 11 Jan 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-26118 in the wild and no public exploit code.

Affected product: n/a. 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-26118/ (Markdown: https://insights.sbomify.com/CVE-2020-26118/index.md)
```

## Sources

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

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