CVE-2026-2074: A vulnerability was identified in O2OA up to 9.0.0

Q: How do I fix CVE-2026-2074?

o2oa: upgrade to newer than 9.0.0. Exact commands for each OS are on this page.

Q: Is CVE-2026-2074 being exploited?

CVE-2026-2074 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-2074 affect?

CVE-2026-2074 affects o2oa. Severity is medium (CVSS 6.3). A vulnerability was identified in O2OA up to 9.0.0. This impacts an unknown function of the file /x_program_center/jaxrs/mpweixin/check of the component HTTP POST Request Handler. The manipulation leads to xml external entity reference. It

Q: How urgent is CVE-2026-2074?

Priority 33/100. Public exploit reference

Routine

MEDIUM 6.3UPGRADE

CVE-2026-2074 is a medium-severity flaw (CVSS 6.3) affecting o2oa. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A vulnerability was identified in O2OA up to 9.0.0. This impacts an unknown function of the file /x_program_center/jaxrs/mpweixin/check of the component HTTP POST Request Handler. The manipulation leads to xml external entity reference. It is possible to initiate the attack remotely. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	6.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.3% (top 76%)
CISA exploited list	No
Weakness	CWE-610, CWE-611
Published	2026-02-07
Last modified	2026-06-17

Publisher (CNA): VulDB · Vendor: zoneland

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-02-07 05:16 UTCPublished CVE record published
2026-06-17 10:30 UTCUpdated Record last modified

zoneland o2oa UPGRADE

Affected: <= 9.0.0

Fixed in: newer than 9.0.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy o2oa || rpm -q o2oa || o2oa --version

2. UPGRADE to newer than 9.0.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade o2oa

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade o2oa

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-2074?

o2oa: upgrade to newer than 9.0.0. Exact commands for each OS are on this page.

Is CVE-2026-2074 being exploited?

CVE-2026-2074 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-2074 affect?

CVE-2026-2074 affects o2oa. Severity is medium (CVSS 6.3). A vulnerability was identified in O2OA up to 9.0.0. This impacts an unknown function of the file /x_program_center/jaxrs/mpweixin/check of the component HTTP POST Request Handler. The manipulation leads to xml external entity reference. It

How urgent is CVE-2026-2074?

Priority 33/100. Public exploit reference

Related CVEs

CVE-2025-9680 LOW 3.5 UPGRADE A vulnerability was detected in O2OA up to 10.0-410
CVE-2025-9681 LOW 3.5 UPGRADE A flaw has been found in O2OA up to 10.0-410
CVE-2025-9682 LOW 3.5 UPGRADE A vulnerability has been found in O2OA up to 10.0-410
CVE-2025-9683 LOW 3.5 UPGRADE A vulnerability was found in O2OA up to 10.0-410
CVE-2025-9715 LOW 3.5 UPGRADE A vulnerability was found in O2OA up to 10.0-410

References

← Back to latest CVEs