# CVE-2021-26295: RCE vulnerability in latest Apache OFBiz due to Java serialisation using RMI

> Unauthenticated attackers can achieve remote code execution and take over Apache OFBiz via unsafe Java deserialization in RMI.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Mar 2021
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-hp7h-f9pw-x5wj

## What is CVE-2021-26295?

CVE-2021-26295 is a critical unsafe deserialization vulnerability in Apache Ofbiz, published on 22 Mar 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Apache OFBiz has unsafe deserialization prior to 17.12.06. An unauthenticated attacker can use this vulnerability to successfully take over Apache OFBiz.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2021-26295?

It affects 1 product.


Products: Apache Ofbiz.

## How do I fix CVE-2021-26295?

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

## Is CVE-2021-26295 being exploited?

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

Public exploit code:

- https://github.com/yumusb/CVE-2021-26295 (github_poc): https://github.com/yumusb/CVE-2021-26295
- CVE-2020-9496和CVE-2021-26295利用dnslog批量验证漏洞poc及exp (github_poc): https://github.com/yuaneuro/ofbiz-poc
- CVE-2021-26295 Apache OFBiz rmi反序列化POC (github_poc): https://github.com/rakjong/CVE-2021-26295-Apache-OFBiz
- Apache OFBiz SOAP Java Deserialization (metasploit)
- CVE-2021-26295 EXP 可成功反弹Shell (github_poc): https://github.com/dskho/CVE-2021-26295
- CVE-2021-26295-POC 利用DNSlog进行CVE-2021-26295的漏洞验证。  使用 poc：将目标放于target.txt后运行python poc.py即可。（Jdk环境需<12，否则ysoserial无法正常生成有效载荷）  exp：python exp.py https://baidu.com然后进入命令执行界面（无回显） (github_poc): https://github.com/coolyin001/CVE-2021-26295--

## Other vulnerabilities in Apache Ofbiz

- [CVE-2024-45195](https://insights.sbomify.com/CVE-2024-45195/): Apache OFBiz Forced Browsing (critical 9.8, exploited in the wild)
- [CVE-2024-32113](https://insights.sbomify.com/CVE-2024-32113/): Apache OFBiz Path Traversal (critical 9.1, exploited in the wild)
- [CVE-2024-38856](https://insights.sbomify.com/CVE-2024-38856/): Apache OFBiz Incorrect Authorization (high 8.1, exploited in the wild)
- [CVE-2013-2250](https://insights.sbomify.com/CVE-2013-2250/): Code injection in n/a (critical 10.0)
- [CVE-2012-3506](https://insights.sbomify.com/CVE-2012-3506/): Unspecified vulnerability in the Apache Open For Business Project (aka OFBiz) 10.04.x before 10.04.03 has unknown impact and attack vectors. (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-26295 and fix it if it is affected.

What it is: CVE-2021-26295 is a critical unsafe deserialization vulnerability in Apache Ofbiz, published on 22 Mar 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-26295 exists.

Affected product: Apache Ofbiz. 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-2021-26295/ (Markdown: https://insights.sbomify.com/CVE-2021-26295/index.md)
```

## Sources

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

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