Skip to main content

CVE-2026-127286Zackriya-Solutions Meetily improper authentication

Low priorityMedium5.5EPSS not scored yet

CVE-2026-127286 is a improper authentication in Zackriya-Solutions Meetily, rated medium (5.5 on CVSS 4.0).

Why this priority: Medium severity, with no exploitation signal.

Published · Updated · NVD status: Deferred

What it is

The software does not prove who a caller is, so an attacker can pass as someone else. A function that should require sign-in can be called by anyone.

How it is reached

An attacker can exploit it over the network, without an account, and nobody has to click anything.

What an attacker gains

The direct impact is limited: partial access to data or a partial outage. In practice, this kind of flaw lets an attacker act as a signed-in user, or an administrator, without valid credentials.

Is it being exploited?

There is no public report of exploitation yet.

What to do

  1. No fixed version is listed yet. Find every place Zackriya-Solutions Meetily runs, watch the references for a fix, and plan a replacement if it is no longer supported.
  2. While there is no fix, keep it off the internet or behind a VPN, allowlist or authenticating proxy.

Description from NVD

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."

What this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

  • Sign-in, session and token handling. The flaw sits between anonymous callers and authenticated sessions.
  • Identity providers and SSO. The flaw sits between anonymous callers and authenticated sessions.

Trust boundaries in play

  • Internet-facing entry points. No account is needed. Any instance reachable from outside your perimeter, through a load balancer, gateway, VPN or exposed admin port, is in scope.
  • Between anonymous callers and authenticated sessions. An attacker who crosses it can act as a signed-in user, or an administrator, without valid credentials.

Questions to answer about your own systems

  • Where does Zackriya-Solutions Meetily run in your systems, and at which version?
  • Which of those instances can be reached from the internet or partner networks?
  • What can it reach once compromised: which data stores, secrets and services?

Sources

  • CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
  • Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
  • Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
  • Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.