Skip to main content
VulnerabilityPublished

CVE-2026-19010: TinyAGI · Missing Authorization

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-19010· Medium 6.9

Public exploit available · CVSS 6.9 Medium.

Data as of 5 Nov 2026, 00:01 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
TinyAGIAffected
  • =0.0.20
Fixed in–
GitHubtinyagi/tinyagipkg:github/tinyagi/tinyagiOther threatsAffected
  • =0.0.20
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should monitor the vendor or project repository for updates and apply any forthcoming patches promptly. Until a fix is released, consider restricting access to the vulnerable API endpoint or implementing additional access controls to mitigate unauthorized usage.

Description

A security vulnerability (CVE-2026-19010) exists in TinyAGI version 0.0.20 within the processMessage function of the Message API Endpoint component. This flaw allows remote attackers to bypass authorization checks, potentially leading to unauthorized access. The vulnerability has a high severity score of 7.3 (CVSS 3.1) and has been publicly disclosed. The project has been notified but has not yet issued a response or patch.

References

Community reviews

Loading reviews…