CVE-2025-53914
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 · uneditedExcessive Privileges vulnerability in Calix GigaCenter ONT (Broadcom SoC modules) allows Privilege Abuse.This issue affects GigaCenter ONT: 844E, 844G, 844GE, 854GE, 812G, 813G, 818G.
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 confidenceCalix GigaCenter ONT devices (models 844E, 844G, 844GE, 854GE, 812G, 813G, 818G) based on Broadcom SoC modules contain an excessive privileges vulnerability allowing privilege abuse. Users or processes can perform actions beyond their intended authorization level.
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
- Physical
- Complexity
- Low
- Privileges
- None
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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 GigaCenter ONT device modelAccess the device management interface or CLI and retrieve the exact model number (844E, 844G, 844GE, 854GE, 812G, 813G, or 818G)Affected if The device model matches one of the affected models listed in the CVE (844E, 844G, 844GE, 854GE, 812G, 813G, or 818G)
-
Retrieve the device firmware versionAccess the device management interface or CLI and run the command to display firmware version (for example, 'show version' or check the system status page)Affected if The device runs a firmware version that falls within any affected version range (compare your version against the ranges provided by Calix for this CVE)
-
Review all user accounts on the deviceAccess the device user management section (typically in Settings > Users or via CLI command 'show users') and list all configured accountsAffected if There are user accounts present that should not exist or that were not created by an authorized administrator
-
Audit assigned privilege levelsFor each user account, check the assigned privilege level, role, or access group (typically found in the user management interface under privileges or access rights)Affected if Any user account has a privilege level higher than expected for their role, or users have administrative/root privileges they should not possess
-
Verify least-privilege configurationCross-reference each user's assigned privileges against the principle of least-privilege: confirm users can only access features and perform actions necessary for their job functionAffected if Users have the ability to perform administrative or privileged actions beyond their intended authorization level
The device is affected if it is a Calix GigaCenter ONT model 844E, 844G, 844GE, 854GE, 812G, 813G, or 818G running a vulnerable firmware version and has user accounts with elevated privileges beyond their intended authorization level.
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 dataContact Calix for available firmware updates addressing this vulnerability. In the interim, enforce network segmentation to limit exposure and audit user/account privileges to ensure least-privilege principles are applied.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-53914 — 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-53914 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