CVE-2023-41628: An issue in O-RAN Software Community E2 G-Release allows attackers to cause a Denial of Service (DoS) by incor

This week

HIGH 7.5REMOTEDOWNGRADE

CVE-2023-41628 is a high-severity flaw (CVSS 7.5) affecting e2. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

An issue in O-RAN Software Community E2 G-Release allows attackers to cause a Denial of Service (DoS) by incorrectly initiating the messaging procedure between the E2Node and E2Term components.

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.9% (top 20%)
CISA exploited list	No
Published	2023-09-01
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: o-ran-sc

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

Am I affected?

Timeline

2023-09-01 17:15 UTCPublished CVE record published
2026-06-17 06:22 UTCUpdated Record last modified

o-ran-sc e2 DOWNGRADE

Affected: g-release

Fixed in: no fixed release known

Safe to downgrade to: a release before g-release

1. Check installed version

apt-cache policy e2 || rpm -q e2 || e2 --version

2. No fixed release: DOWNGRADE to a release before g-release (Debian / Ubuntu)

apt-cache madison e2 sudo apt install e2=<VERSION_BEFORE_g-release> sudo apt-mark hold e2

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list e2 sudo dnf downgrade e2-<VERSION_BEFORE_g-release> sudo dnf versionlock add e2

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-2023-41628?

e2: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2023-41628 being exploited?

CVE-2023-41628 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-2023-41628 affect?

CVE-2023-41628 affects e2. Severity is high (CVSS 7.5). An issue in O-RAN Software Community E2 G-Release allows attackers to cause a Denial of Service (DoS) by incorrectly initiating the messaging procedure between the E2Node and E2Term components.

How urgent is CVE-2023-41628?

Priority 56/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

References

← Back to latest CVEs