Skip to main content
VulnerabilityPublished

CVE-2026-19011: TinyAGI · File Inclusion

Affects TinyAGISource CVE Database V5

0
Compare

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.5% chance of exploitation in 30 days – higher than 45% 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:N/VA:N/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–

CPE configurations (1)

  • cpe:2.3:a:tinyagi:tinyagi:*:*:*:*:*:*:*:*

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

AI-suggested

Since the project has not responded or released a fix, users should monitor official channels for updates. Until a patch is available, consider restricting access to the affected functionality or applying temporary controls to limit exposure.

Description

A vulnerability was detected in TinyAGI 0.0.20. The affected element is the function buildSystemPrompt of the file packages/server/src/routes/agents.ts. Performing a manipulation results in file inclusion. The attack may be initiated remotely. The exploit is now public and may be used. The project was informed of the problem early through an issue report but has not responded yet.

References

Community reviews

Loading reviews…