# CVE-2025-15567: Missing authorization in Health

> Attackers can access sensitive health data due to missing authorization checks in the vivo Health application.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Feb 2026
- **Updated:** 27 Feb 2026
- **Also known as:** GHSA-8fxc-329r-9p4v

## What is CVE-2025-15567?

CVE-2025-15567 is a medium-severity missing authorization vulnerability in vivo Health, published on 27 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Insufficient protection mechanisms in the Health Module may lead to partial information disclosure.

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

## Which versions are affected by CVE-2025-15567?

It affects 1 product.


Products: Vivo Health Module.

## How do I fix CVE-2025-15567?

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

## Is CVE-2025-15567 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-15567 and fix it if it is affected.

What it is: CVE-2025-15567 is a medium-severity missing authorization vulnerability in vivo Health, published on 27 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-2025-15567 in the wild and no public exploit code.

Affected product: vivo Health. 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-2025-15567/ (Markdown: https://insights.sbomify.com/CVE-2025-15567/index.md)
```

## Sources

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

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