# CVE-2026-41931: Vvveb < 1.0.8.2 Information Disclosure via Debug Exception Handler

> Unauthenticated attackers can trigger exceptions in the password-reset module to expose server paths and source code via debug handlers.

- **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:** 6 May 2026
- **Updated:** 28 Jul 2026
- **Also known as:** GHSA-xgvg-r47g-786r

## What is CVE-2026-41931?

CVE-2026-41931 is a medium-severity vulnerability in givanz Vvveb, published on 6 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vvveb before version 1.0.8.2 contains an information disclosure vulnerability that allows unauthenticated attackers to obtain sensitive server information by triggering unhandled exceptions in the password-reset module. Attackers can access the admin password-reset endpoint to trigger a fatal error caused by a missing namespace import, which exposes the absolute server file path, internal class namespaces, line numbers, and source code excerpts through the debug exception handler rendered to unauthenticated requests.

Weakness: CWE-209 (Generation of Error Message Containing Sensitive Information), CWE-1188 (Initialization of a Resource with an Insecure Default)

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


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

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

## Is CVE-2026-41931 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-41931 is a medium-severity vulnerability in givanz Vvveb, published on 6 May 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-41931 exists.

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

## Sources

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

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