CVE-2026-25781
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 · uneditedin OpenHarmony v6.0 and prior versions allow a local attacker cause DOS and it cannot be recovered.
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 · low confidenceOpenHarmony v6.0 and prior versions contain a local vulnerability that allows an attacker to cause a Denial of Service condition that persists and cannot be recovered, likely through a crash or resource exhaustion that leaves the system in a non-functional state requiring manual intervention.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
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 OpenHarmony system and versionRun 'grep -i openharmony /etc/os-release' or check system settings > about device to find the OpenHarmony versionAffected if The system runs OpenHarmony and the version is 6.0 or lower (e.g., 5.0, 4.x, 3.x)
-
Confirm local access exists on the deviceCheck for local user accounts, shell access, or physical access possibilities. Review /etc/passwd for local users and check if debug/adb interfaces are enabledAffected if Local user accounts exist, debug features are enabled, or physical access to the device is possible by an attacker
-
Verify system persists across rebootsCheck system integrity by examining critical system partitions and services that should start automatically after a reboot using 'ls -la /etc/init.d/' or similar service listing commandsAffected if The system shows signs of persistent modification that survives reboot, indicating possible exploitation
-
Review system logs for crash or corruption evidenceExamine system logs in /var/log/ or equivalent for entries around unexpected reboots, kernel panics, or service failures that occurred without clear causeAffected if Logs show unexplained crashes, kernel failures, or resource exhaustion events on a system running OpenHarmony v6.0 or prior
A system is affected if it runs OpenHarmony version 6.0 or prior and an attacker could gain local access to execute code that causes persistent system failure surviving reboot.
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 available patches for OpenHarmony v6.0; if no patch exists, isolate affected systems and work with vendors to obtain a fix. Restrict local access to trusted personnel only to limit exposure.
- Consultation4.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 $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25781 — 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-25781 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