How severe is CVE-2022-25767?

CVE-2022-25767 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-25767?

CVE-2022-25767 affects the following packages: com.bstek.ureport:ureport2-console (Maven). Ecosystems affected: Maven.

How do I fix CVE-2022-25767?

The records we use list no patched version of com.bstek.ureport:ureport2-console for CVE-2022-25767. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect CVE-2022-25767 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.bstek.ureport:ureport2-console, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-25767 if there is no patch (or I can't update yet)?

Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Is CVE-2022-25767 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2022-25767, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2022-25767?

CVE-2022-25767 has an EPSS (Exploit Prediction Scoring System) score of 3.2%, placing it in the 88th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-25767?

CVE-2022-25767 is classified as Deserialization of Untrusted Data (CWE-502). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2022-25767 published, and has it been updated?

CVE-2022-25767 was published on May 3, 2022 and was last updated on March 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

CRITICAL severity

CVE-2022-25767 — ureport2-console

CRITICAL

CVE-2022-25767 is a critical-severity (CVSS 9.8) Deserialization of Untrusted Data vulnerability in com.bstek.ureport:ureport2-console. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Deserialization of Untrusted Data in com.bstek.ureport:ureport2-console

Published

May 3, 2022

Updated

Mar 16, 2026

Affected

1 pkg

Patched

See advisory

Exploits

1 known

Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

3.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs88th percentile — riskier than 88% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

☕com.bstek.ureport:ureport2-console

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

All versions of package com.bstek.ureport:ureport2-console are vulnerable to Remote Code Execution by connecting to a malicious database server, causing arbitrary file read and deserialization of local gadgets.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.bstek.ureport:ureport2-console`	all versions	No fix

Affected Products

1 product · 1 configurations

Application

ureport2ureport2_project

all

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

All versions of package com.bstek.ureport:ureport2-console are vulnerabl…

github.comNVDMay 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.bstek.ureport:ureport2-console, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of com.bstek.ureport:ureport2-console for CVE-2022-25767. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2022-25767 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

9.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CWE Classification

CWE-502Deserialization of Untrusted Data

Weaponization

No Nuclei template or Metasploit module yet. 1 public proof-of-concept reference is listed on this page.

Timeline

Disclosed

May 3, 2022

First exploit

May 11, 2022

Last updated

Mar 16, 2026

Identifiers

CVE-2022-25767

References

Advisorynvd.nist.gov · CVE 2022 25767 Webgithub.com · ureport2 console.md Websnyk.io · SNYK JAVA COMBSTEKUREPORT 2322018 Packagegithub.com · ureport

Related vulnerabilities

Also affects ureport2-console

This CVE is critical severity — higher than any of the other 1 CVE affecting ureport2-console (highest there: high).

CVE-2020-21122

Same weakness: CWE-502

This CVE is critical severity; 1 of 7 other CVEs with CWE-502 is rated as high or higher (top: critical).

CVE-2026-114151CVE-2026-126187CVE-2026-115878CVE-2026-62848CVE-2026-115912CVE-2026-116580CVE-2026-114608Browse all CWE-502

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedMar 16, 2026

CVE-2022-25767 — ureport2-console

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Remediation status

Mitigate without a patch

Frequently Asked Questions

Is CVE-2022-25767 in your dependencies?