CVE-2026-26102
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 · uneditedIncorrect Permission Assignment for Critical Resource in Owl opds 2.2.0.4 allows File Manipulation via a crafted network request.
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 confidenceOwl opds version 2.2.0.4 contains a permission misconfiguration that allows authenticated or unauthenticated attackers to manipulate files on the server via crafted network requests. The vulnerability stems from incorrect permission assignment to critical resources, enabling arbitrary file write, modification, or deletion capabilities.
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= 2.2.0.4CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 OPDS versionLocate the application version information - typically found in the web interface footer, an about page, a version file, or via API endpoint like /api/version or /statusAffected if version equals 2.2.0.4 exactly
-
Verify network interface exposureCheck if the OPDS web server is listening on exposed network interfaces (check configuration files or running processes for binding to 0.0.0.0 or publicly accessible IPs)Affected if network interface is accessible from untrusted networks without proper firewall restrictions
-
Inspect file operation endpointsReview the application's API endpoints or configuration for file upload, write, or delete functionalities (look for endpoints handling file paths, uploads, or file operations in the API or web route configuration)Affected if file operation endpoints exist and are accessible without proper authorization controls
-
Examine file permission configurationCheck the application's file handling configuration or permission files for how critical resources are protected (look for permission assignments in config files related to file access, storage paths, or resource authorization)Affected if file permissions are set to allow unrestricted access to critical system resources or user data files
You are affected if the installed Owl OPDS version is exactly 2.2.0.4 and the network interface or file operation endpoints are accessible, as the permission misconfiguration enables arbitrary file manipulation.
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 dataReview and correct file permission assignments in the application's file handling logic, implement proper authorization checks before file operations, and restrict file access to least-privilege principles.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-26102 — 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-26102 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