# CVE-2026-8990: Authentication Bypass in Kidsview

> An attacker with physical access can bypass authentication via push notifications to gain full access to the device owner's account.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:P/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/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:** 28 May 2026
- **Updated:** 28 May 2026
- **Also known as:** GHSA-frf3-pwqj-2qf5

## What is CVE-2026-8990?

CVE-2026-8990 is a medium-severity authentication bypass vulnerability in Kidsview, published on 28 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A user with physical access to a smartphone can bypass authentication mechanism of Kidsview mobile application and grant himself full access to the device owner's account by interacting with application's push notification.

This issue was fixed in version 4.4.3

Weakness: CWE-359 (Exposure of Private Personal Information to an Unauthorized Actor), CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

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


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

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

## Is CVE-2026-8990 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-8990 is a medium-severity authentication bypass vulnerability in Kidsview, published on 28 May 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-8990 in the wild and no public exploit code.

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

## Sources

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

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