Skip to content
Fencer Vulns
high 8.8

CVE-2022-0981 json

A flaw was found in Quarkus.

published 2022-03-23 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-15978

cvss
8.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.2%
EPSS 1.2% chance of exploitation in 30 days, percentile 67%
public exploits
0
none known

Summary

A flaw was found in Quarkus. The state and potentially associated permissions can leak from one web request to another in RestEasy Reactive. This flaw allows a low-privileged user to perform operations on the database with a different set of privileges than intended.

Patch / fix

  • quarkus quarkus 2.7.1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-0981 updated cvss 7.6

quarkus: privilege escalation vulnerability with RestEasy Reactive scope leakage in Quarkus

  • Red Hat Integration Camel K 1 quarkus quarkus Red Hat Integration Camel Quarkus 1 quarkus quarkus
    affected: no fix available
  • Red Hat build of Quarkus 2.7.5
    fixed: vendor fix RHSA-2022:4623
  • Red Hat RHINT Camel-Q 2.7
    fixed: vendor fix RHSA-2022:5606
  • Red Hat RHINT Service Registry 2.3.0 GA
    fixed: vendor fix RHSA-2022:6835

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.17% chance of exploitation in the next 30 days, higher than 67% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/quarkusio/quarkus/issues/23269 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 6.5 AV:N/AC:L/Au:S/C:P/I:P/A:P

Affected products

  • n/a quarkus

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.