# CVE-2026-55417: Chevereto private profile setting leaks username on /json endpoint

> Unauthenticated attackers can retrieve private usernames and public images via the JSON endpoint, bypassing profile privacy settings.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jul 2026
- **Updated:** 8 Jul 2026
- **Also known as:** GHSA-h4jp-mxfx-g8xp

## What is CVE-2026-55417?

CVE-2026-55417 is a medium-severity vulnerability in chevereto, published on 7 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Chevereto is a self-hosted media-sharing platform. Starting in version 3.7.5 and prior to version 4.5.4, when a user enables the private profile option, visiting their profile HTML route (`/username`) correctly returns 404. However, the `/json` AJAX listing endpoint does not apply the same check. An unauthenticated caller who knows the target's user ID can retrieve all of that user's publicly-scoped images, revealing the username (which should be private). This is patched in Chevereto v4.5.4. No known workarounds are available.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-55417 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55417 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-55417 is a medium-severity vulnerability in chevereto, published on 7 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55417 exists.

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

## Sources

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

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