CVE-2026-25658
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 · uneditedEricsson Packet Core Gateway (PCG) versions prior to 1.30 contain an Improper Handling of Missing Values (CWE-230) vulnerability where an attacker continuously sending a specially crafted message can cause service degradation. The impact continues as long the attack persists but the system recovers from the crashes when the attack stops.
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 · high confidenceEricsson Packet Core Gateway versions prior to 1.30 improperly handle missing values in specially crafted messages (CWE-230). An attacker can continuously send these crafted messages to cause service degradation, with recovery occurring only when the attack stops.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.30CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/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.
-
Identify installed Packet Core Gateway versionUse the Ericsson command-line interface or management console to query the software version. Common commands include 'show version' or checking the system information panel in the management GUI.Affected if The displayed version is any version prior to 1.30 (e.g., 1.20, 1.25, 1.29.x)
-
Verify version through system inventoryAccess the system inventory or software management module via the Ericsson Packet Core Gateway administration interface and locate the running software version string.Affected if The version string shows a number less than 1.30 (for example, checking if the major.minor version is below 1.30)
-
Check service health statusReview the Packet Core Gateway service health metrics through the monitoring dashboard or by running 'show service status' or equivalent health check command.Affected if Service shows degraded performance, elevated error rates, or abnormal resource usage without an otherwise explained cause
-
Inspect message handling logsExamine the packet gateway logs for patterns of malformed messages or repeated parsing errors. Look for log entries indicating missing value handling failures.Affected if Logs contain repeated warnings or errors related to missing values in received messages, especially in high volume
-
Review network traffic for crafted messagesCapture and analyze network traffic reaching the Packet Core Gateway for suspicious messages with malformed or missing fields, particularly in a continuous pattern.Affected if Network capture shows a pattern of specially crafted messages with missing mandatory values being received by the gateway
A user is affected if their installed Ericsson Packet Core Gateway version is below 1.30 and they observe service degradation linked to malformed messages with missing values.
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.
dbcve · scoped1.30
Upgrade Ericsson Packet Core Gateway to version 1.30 or later to remediate this vulnerability.
1.30
- Contact Ericsson support to obtain the Packet Core Gateway version 1.30 upgrade package
- Review Ericsson upgrade documentation for PCG 1.30
- Schedule a maintenance window for the upgrade process
- Back up current PCG configuration according to Ericsson best practices
- Upgrade Packet Core Gateway to version 1.30 or later
- Verify the upgrade was successful and services are operational
- Monitor system for any anomalies following the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation4.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 $6,784.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25658 — 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-2026-25658 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