CVE-2025-57446
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn issue in O-RAN Near Realtime RIC ric-plt-submgr in the J-Release environment, allows remote attackers to cause a denial of service (DoS) via a crafted request to the Subscription Manager API component.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe vulnerability exists in the O-RAN Near Realtime RIC Subscription Manager (ric-plt-submgr) component in the J-Release environment. Remote attackers can send crafted requests to the Subscription Manager API to trigger a denial of service condition, likely due to improper input handling or resource exhaustion.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate ric-plt-submgr componentIdentify if the ric-plt-submgr (Subscription Manager) process or service is running in your O-RAN Near Realtime RIC environment. Check process lists, containerized deployments, or service manifests for this component.Affected if The ric-plt-submgr component is present and active in your environment
-
Confirm J-Release environmentDetermine which O-RAN RIC release your deployment is using. Check your deployment configuration files, version metadata, or release tags to verify if you are on the J-Release branch.Affected if Your RIC platform is running the J-Release version
-
Verify API accessibilityInspect network configuration and firewall rules to determine if the Subscription Manager API endpoint is exposed to network access. Check for exposed ports or API gateway configurations.Affected if The Subscription Manager API is network-accessible from untrusted sources
-
Review for DoS indicatorsExamine system logs, service health metrics, and API request logs for unusual patterns such as service crashes, high resource usage, or failed requests that may indicate exploitation of this vulnerability.Affected if You observe abnormal API behavior, service failures, or resource exhaustion patterns consistent with denial of service conditions
You are likely affected if the ric-plt-submgr component is running in a J-Release environment and its API is accessible, especially if you notice DoS symptoms in logs or metrics.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor-provided patches or updates to the ric-plt-submgr component in the O-RAN Near Realtime RIC. If no patch is available, implement rate limiting and request validation at the API ingress point to mitigate malformed request exploitation.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-57446 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-57446 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data