# CVE-2026-127286: Zackriya-Solutions Meetily main.py missing authentication


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-x2r4-mx29-qfc3

## What is CVE-2026-127286?

CVE-2026-127286 is a medium-severity vulnerability in Zackriya-Solutions Meetily, published on 13 Nov 2026. 

### Official description

A vulnerability was identified in Zackriya-Solutions Meetily up to 0.4.1. Affected is an unknown function of the file backend/app/main.py. The manipulation leads to missing authentication. The attack is possible to be carried out remotely. The exploit is publicly available and might be used. The legacy backend was not removed yet. Vulnerable code is still present on main. The vendor explains: "[W]e are moving towards a single unified application using the tauri framework, and we deprecated the client-server architecture of this application."

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

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

It affects 1 product.


Products: Zackriya-Solutions Meetily.

CPE match criteria (CPE 2.3):

- `cpe:2.3:a:zackriya-solutions:meetily:*:*:*:*:*:*:*:*` from 0.4.0 up to 0.4.0
- `cpe:2.3:a:zackriya-solutions:meetily:*:*:*:*:*:*:*:*` from 0.4.1 up to 0.4.1

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

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

## Is CVE-2026-127286 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-127286 is a medium-severity vulnerability in Zackriya-Solutions Meetily, published on 13 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-127286 in the wild and no public exploit code.

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

## Sources

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

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