Skip to content
statance
MenuClose
Log inStart for free ↗
high · CVSS 7.4

CVE-2026-89058

Resteasy-core: resteasy: corsfilter reflects arbitrary origin with credentials under wildcard config

Published 18 Sept 2026 · Source updated 6 Nov 2026 · Retrieved 2026-11-06 01:53 UTC

Statance checks for CVE-2026-89058. Connected servers are checked automatically against the fixed versions their distribution or package ecosystem has published for it, including app dependency lockfiles. Check my servers ↗
Monitor this CVE ↗Full CVE monitoring on Pro and Business

What happened?

A flaw was found in RESTEasy's CorsFilter, which, when configured to allow all origins ("*"), reflects the request's Origin header back in the Access-Control-Allow-Origin response together with Access-Control-Allow-Credentials: true. This permissive cross-origin policy allows a malicious website to make credentialed cross-origin requests and read authenticated responses from a victim's session, resulting in a loss of confidentiality.

Description supplied by CVE Program. Formatting is simplified; follow the original advisory for full details.

Affected software and versions

Source-provided software and version information
SoftwareVersion informationFixed version
RESTEasyRed Hataffected: 0 to < 6.2.19.Final; affected: 7.0.0.Alpha1 to < 7.0.5.FinalSee vendor advisory
org.jboss.resteasy/resteasy-coreRed Hatunaffected: 6.2.19.Final-redhat-00003 to < *See vendor advisory
org.jboss.resteasy/resteasy-coreRed Hatunaffected: 6.2.19.Final-redhat-00003 to < *See vendor advisory
org.jboss.resteasy/resteasy-coreRed Hatunaffected: 6.2.19.Final-redhat-00003 to < *See vendor advisory
dogtag-pkiRed Hatunaffected: 0:11.9.0-6.el10_2.1 to < *See vendor advisory
dogtag-pkiRed Hatunaffected: 0:11.6.0-3.el10_0.2 to < *See vendor advisory
resteasyRed Hatunaffected: 0:3.0.26-20.el9_8.1 to < *See vendor advisory
resteasyRed Hatunaffected: 0:3.0.26-20.el9_4.2 to < *See vendor advisory
resteasyRed Hatunaffected: 0:3.0.26-20.el9_6.2 to < *See vendor advisory
resteasy-coreRed HatDefault status: unaffectedSee vendor advisory
resteasy-coreRed HatDefault status: affectedSee vendor advisory
resteasy-coreRed HatDefault status: affectedSee vendor advisory
resteasy-coreRed HatDefault status: affectedSee vendor advisory
resteasy-coreRed HatDefault status: affectedSee vendor advisory
rhbk/keycloak-rhel9-operatorRed HatDefault status: affectedSee vendor advisory
redhat-pki:10/redhat-pkiRed HatDefault status: affectedSee vendor advisory
redhat-pkiRed HatDefault status: affectedSee vendor advisory
pki-core:10.6/pki-coreRed HatDefault status: unaffectedSee vendor advisory
jackson-jaxrs-providersRed HatDefault status: unaffectedSee vendor advisory
pki-coreRed HatDefault status: unaffectedSee vendor advisory
resteasy-coreRed HatDefault status: affectedSee vendor advisory
resteasy-jaxrsRed HatDefault status: affectedSee vendor advisory
jboss-eap-7/eap74-els-openjdk11-openshift-rhel8Red HatDefault status: affectedSee vendor advisory
jboss-eap-7/eap74-els-openjdk17-openshift-rhel8Red HatDefault status: affectedSee vendor advisory
jboss-eap-7/eap74-els-openjdk8-openshift-rhel8Red HatDefault status: affectedSee vendor advisory
resteasy-jaxrsRed HatDefault status: affectedSee vendor advisory
resteasy-coreRed HatDefault status: affectedSee vendor advisory
resteasy-coreRed HatDefault status: affectedSee vendor advisory
candlepinRed HatDefault status: unaffectedSee vendor advisory
resteasy-jaxrsRed HatDefault status: affectedSee vendor advisory

Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.

Is it being exploited?

This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.

CISA data retrieved 2026-11-06 16:38 UTC. Check CISA ↗

How to respond

  1. Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
  2. Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
  3. Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.

Sources and remediation references

This public advisory does not determine whether a particular server is affected. Records are refreshed as sources change; verify urgent decisions against the original advisory.

← Browse the public CVE feed