# CVE-2026-42095: Missing authorization in Arianna

> Attackers can read arbitrary files via socket connection by guessing URLs due to missing authentication in KDE Arianna bookserver.

- **Severity:** Medium 4.0 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Apr 2026
- **Updated:** 24 Apr 2026
- **Also known as:** DEBIAN-CVE-2026-42095, GHSA-7824-f4f9-2x77, UBUNTU-CVE-2026-42095, openSUSE-SU-2026:10653-1

## What is CVE-2026-42095?

CVE-2026-42095 is a medium-severity missing authorization vulnerability in KDE Arianna, published on 24 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

bookserver in KDE Arianna before 26.04.1 allows attackers to read files over a socket connection by guessing a URL.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `arianna` | openSUSE:Tumbleweed | All versions | 26.04.0-2.1 |

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

Upgrade to a fixed version.

## Is CVE-2026-42095 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-42095 is a medium-severity missing authorization vulnerability in KDE Arianna, published on 24 Apr 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-42095 in the wild and no public exploit code.

Affected product: KDE Arianna. 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-42095/ (Markdown: https://insights.sbomify.com/CVE-2026-42095/index.md)
```

## Sources

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

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