CVE-2026-25657
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 Syntactically Invalid Structure (CWE-228) 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 · moderate confidenceEricsson Packet Core Gateway versions prior to 1.30 contain a CWE-228 vulnerability where the software improperly handles syntactically invalid structure. An attacker can continuously send specially crafted messages to cause service degradation, with the system recovering only when the attack ceases.
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 the installed Ericsson Packet Core Gateway versionConsult your system's version reporting mechanism (such as the command line interface, management console, or version information file) to obtain the exact installed version of Ericsson Packet Core Gateway.Affected if The installed version is anything prior to 1.30 (for example, 1.20, 1.25, 1.28.x)
-
Confirm the version is within the affected rangeCompare the identified version number against the vulnerable range: versions less than 1.30 are affected by this vulnerability.Affected if The version is below 1.30 (the version number is lower than 1.30)
-
Determine if network-exposed interfaces are accessibleReview network configuration to identify whether the Packet Core Gateway management or signaling interfaces are reachable from untrusted networks, as the attack requires sending specially crafted messages to the system.Affected if External or untrusted network access to the gateway is possible and the version is below 1.30
A system is affected if it runs any version of Ericsson Packet Core Gateway prior to version 1.30 and has network accessibility that allows an attacker to send malformed messages to the gateway.
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. Consider implementing traffic filtering or rate limiting on ingress interfaces as a compensating control until the upgrade can be performed.
Version 1.30
- 1. Identify the current installed version of Ericsson Packet Core Gateway
- 2. Review Ericsson upgrade documentation for Packet Core Gateway
- 3. Schedule a maintenance window for the upgrade
- 4. Create a full backup of the current PCG configuration
- 5. Upgrade Ericsson Packet Core Gateway to version 1.30 or later
- 6. Verify the upgrade was successful by checking the version number
- 7. Confirm normal service operation after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2026-25657 — 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-25657 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