How severe is CVE-2016-6345?

CVE-2016-6345 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2016-6345?

CVE-2016-6345 affects the following packages: org.jboss.resteasy:resteasy-client (Maven), org.jboss.resteasy:resteasy-client (Maven). Ecosystems affected: Maven.

How do I fix CVE-2016-6345?

Update org.jboss.resteasy:resteasy-client to 3.0.20.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2016-6345 is resolved across your whole dependency graph.

How do I detect CVE-2016-6345 in my Maven dependencies?

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

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

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is CVE-2016-6345 actively exploited in the wild?

No public exploit code has been indexed for CVE-2016-6345 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2016-6345?

CVE-2016-6345 has an EPSS (Exploit Prediction Scoring System) score of 1.8%, placing it in the 78th 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-2016-6345?

CVE-2016-6345 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2016-6345 published, and has it been updated?

CVE-2016-6345 was published on September 7, 2016 and was last updated on March 14, 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

MEDIUM severity

CVE-2016-6345 — resteasy-client

MEDIUM

CVE-2016-6345 is a medium-severity (CVSS 6.5) Information Exposure vulnerability in org.jboss.resteasy:resteasy-client. A fix is available for org.jboss.resteasy:resteasy-client — see the affected versions and patch details below.

Exposure of Sensitive Information to an Unauthorized Actor in RESTEasy

Also known asGHSA-vxhj-3x7p-jxp5

Published

Sep 7, 2016

Updated

Mar 14, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs78th percentile — riskier than 78% 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

2 pkgs affected

☕org.jboss.resteasy:resteasy-client☕org.jboss.resteasy:resteasy-client

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

RESTEasy allows remote authenticated users to obtain sensitive information by leveraging "insufficient use of random values" in async jobs.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jboss.resteasy:resteasy-client`	all versions	3.0.20.Final`org.jboss.resteasy:resteasy-client:3.0.20.Final`
☕Maven	`org.jboss.resteasy:resteasy-client`	≥ 3.1.0.Beta1&&< 3.1.0.CR1	3.1.0.CR1`org.jboss.resteasy:resteasy-client:3.1.0.CR1`

Affected Products

1 product · 1 configurations

Application

resteasyredhat

all

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jboss.resteasy:resteasy-client, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jboss.resteasy:resteasy-client to 3.0.20.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2016-6345 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatLow

Workaround published by Red Hat

Don't enable Async Jobs Service as details in the section, "2.10. RESTEASY ASYNCHRONOUS JOB SERVICE" of JBoss EAP 7 Developing Web Services Applications documentation: https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/7.0/paged/developing-web-services-applications/chapter-2-developing-jax-rs-web-services

Source: Red Hat security advisory for CVE-2016-6345 (CC BY 4.0)

Frequently Asked Questions

RESTEasy allows remote authenticated users to obtain sensitive information by leveraging "insufficient use of random values" in async jobs.

O3 Security · Impact-Aware SCA

Is CVE-2016-6345 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Raw vector

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

CWE Classification

CWE-200Information Exposure

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Sep 7, 2016

Last updated

Mar 14, 2026

Identifiers

CVE-2016-6345

GHSA-vxhj-3x7p-jxp5

References

Advisorysecurityfocus.com Advisorynvd.nist.gov · CVE 2016 6345 Reportbugzilla.redhat.com · show bug.cgi

Related vulnerabilities

Also affects resteasy-client

This CVE is medium severity; 6 of 6 other CVEs affecting resteasy-client are rated as high or higher (top: high).

CVE-2020-1695CVE-2016-6348CVE-2016-6347CVE-2012-0818CVE-2014-3490CVE-2020-25633

Same weakness: CWE-200

This CVE is medium severity; 1 of 2 other CVEs with CWE-200 is rated as high or higher (top: moderate).

CVE-2026-55098GHSA-m3qr-fvp4-78xjBrowse all CWE-200

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedMar 14, 2026

CVE-2016-6345 — resteasy-client

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

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2016-6345 in your dependencies?