CVE-2022-41923: Grails Spring Security Core plugin is vulnerable to privilege escalation

This month

CRITICAL 9.1REMOTEUPGRADE

CVE-2022-41923 is a critical-severity flaw (CVSS 9.1) affecting spring security core. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Grails Spring Security Core plugin is vulnerable to privilege escalation. The vulnerability allows an attacker access to one endpoint (i.e. the targeted endpoint) using the authorization requirements of a different endpoint (i.e. the donor endpoint). In some Grails framework applications, access to the targeted endpoint will be granted based on meeting the authorization requirements of the donor endpoint, which can result in a privilege escalatio

Why this priority

Critical severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.1 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.9% (top 20%)
CISA exploited list	No
Weakness	CWE-269, CWE-863
Published	2022-11-23
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: grails

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

Am I affected?

Timeline

2022-11-23 19:15 UTCPublished CVE record published
2026-06-17 05:04 UTCUpdated Record last modified

grails spring security core UPGRADE

Affected: >= 1.0 and < 3.3.2 · >= 4.0.0 and < 4.0.5 · >= 5.0.0 and < 5.1.1

Fixed in: 3.3.2, 4.0.5, 5.1.1

Safe to downgrade to: a release before 1.0

1. Check installed version

apt-cache policy spring-security-core || rpm -q spring-security-core || spring-security-core --version

2. UPGRADE to 3.3.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade spring-security-core

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade spring-security-core

Note

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

3. If no update is available yet, DOWNGRADE to a release before 1.0 (Debian / Ubuntu)

apt-cache madison spring-security-core sudo apt install spring-security-core=<VERSION_BEFORE_1.0> sudo apt-mark hold spring-security-core

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list spring-security-core sudo dnf downgrade spring-security-core-<VERSION_BEFORE_1.0> sudo dnf versionlock add spring-security-core

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

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-2022-41923?

spring security core: upgrade to 3.3.2, 4.0.5, 5.1.1. Exact commands for each OS are on this page.

Is CVE-2022-41923 being exploited?

CVE-2022-41923 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-2022-41923 affect?

CVE-2022-41923 affects spring security core. Severity is critical (CVSS 9.1). Grails Spring Security Core plugin is vulnerable to privilege escalation. The vulnerability allows an attacker access to one endpoint (i.e. the targeted endpoint) using the authorization requirements of a different endpoint (i.e. the donor

How urgent is CVE-2022-41923?

Priority 57/100. Critical severity; Remotely exploitable, no login, no user action

References

← Back to latest CVEs