# CVE-2026-26102: Incorrect Permission Assignment for Critical Resource in Owl opds

> Attackers can manipulate files via crafted network requests due to incorrect permission assignments in the Owl OPDS server.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Feb 2026
- **Updated:** 20 Feb 2026
- **Also known as:** GHSA-wqpx-frj2-7xmj

## What is CVE-2026-26102?

CVE-2026-26102 is a high-severity missing authorization vulnerability in Owl opds, published on 20 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Incorrect Permission Assignment for Critical Resource in Owl opds 2.2.0.4 allows File Manipulation via a crafted network request.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2026-26102?

It affects 1 product.


Products: Owlcyberdefense Opds-Talon.

## How do I fix CVE-2026-26102?

No fix has been published for CVE-2026-26102 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-26102 being exploited?

There is no known exploitation of CVE-2026-26102 in the wild and no public exploit code.

## Other vulnerabilities in Owl opds

- [CVE-2026-2333](https://insights.sbomify.com/CVE-2026-2333/): Improper Neutralization of Special Elements used in a Command ('Command Injection') in Owl opds (critical 9.2)
- [CVE-2026-26093](https://insights.sbomify.com/CVE-2026-26093/): Improper Neutralization of Special Elements used in a Command ('Command Injection') in Owl opds (high 8.7)
- [CVE-2026-26095](https://insights.sbomify.com/CVE-2026-26095/): Incorrect Permission Assignment for Critical Resource in Owl opds (high 8.5)
- [CVE-2026-26096](https://insights.sbomify.com/CVE-2026-26096/): Incorrect Permission Assignment for Critical Resource in Owl opds (high 8.5)
- [CVE-2026-26101](https://insights.sbomify.com/CVE-2026-26101/): Incorrect Permission Assignment for Critical Resource in Owl opds (high 8.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-26102 and fix it if it is affected.

What it is: CVE-2026-26102 is a high-severity missing authorization vulnerability in Owl opds, published on 20 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-26102 in the wild and no public exploit code.

Affected product: Owl opds. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-26102/ (Markdown: https://insights.sbomify.com/CVE-2026-26102/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-26102
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-26102
- OSV: https://osv.dev/vulnerability/CVE-2026-26102

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-26102/
Summaries are generated and may contain mistakes; the official description above is the record.