dbcve.org
Opds TalonOperating system · Owlcyberdefense

CVE-2026-26097

MEDIUM · 5.5 CVSS v3.1 Published 2026-02-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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 · unedited
Uncontrolled Search Path Element in Owl opds 2.2.0.4 allows Leveraging/Manipulating Configuration File Search Paths 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 confidence

Owl opds version 2.2.0.4 contains an Uncontrolled Search Path Element vulnerability (CWE-427) where the application uses unsanitized paths when searching for configuration files. An attacker can exploit this by sending crafted network requests to manipulate where the application searches for or loads configuration files, potentially causing it to load malicious configurations from attacker-controlled locations.

MitigationImplement strict path validation and use absolute, hardcoded paths for configuration file locations. Remove or restrict any user-controllable path parameters in configuration file resolution, and ensure configuration files are loaded only from trusted, non-writable locations.

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
Opds TalonOperating system
Affected:= 2.2.0.4

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
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed version of Owl Opds Talon
    Check the product version using the system's package manager, software inventory, or application metadata (often visible in the application UI, about page, or installed binaries)
    Affected if The installed version is exactly 2.2.0.4
  2. Examine configuration file loading mechanisms
    Review application configuration files and logs to determine how and from which paths configuration files are loaded. Look for settings that specify directories or paths used during configuration resolution.
    Affected if Configuration file paths are derived from user-controllable input, environment variables, or unsanitized path settings
  3. Check for path-related parameters in configuration
    Inspect the application's configuration files (e.g., config.xml, settings.conf, or similar) for parameters that control where configuration files are searched for or loaded from
    Affected if Path parameters allow external manipulation or point to writable locations
  4. Verify configuration directory permissions
    Check file system permissions on directories where the application stores or searches for configuration files to ensure they are not writable by untrusted users
    Affected if Configuration directories are writable by untrusted users or processes
  5. Review network request handling for path injection
    Analyze how the application handles network requests that may influence configuration file paths - check if request parameters can influence path resolution
    Affected if Network requests can inject or manipulate paths used for configuration loading
  6. Audit application logs for suspicious configuration loading
    Review application logs for any unusual configuration file loading attempts, particularly from unexpected directories or locations
    Affected if Logs show configuration files being loaded from non-standard or unexpected locations

You are affected if Owl Opds Talon version 2.2.0.4 is installed AND the application allows configuration file paths to be influenced by external input or loads configurations from user-controllable locations.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict path validation and use absolute, hardcoded paths for configuration file locations. Remove or restrict any user-controllable path parameters in configuration file resolution, and ensure configuration files are loaded only from trusted, non-writable locations.

Fix this in Opds Talon Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-26097 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-26097 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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