Skip to main content
VulnerabilityPublished

CVE-2026-18277: Scripta eScriptorium · Missing Authorization

Affects Scripta eScriptoriumSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.1 High : upgrade to 26.04.2 soon.

Data as of 5 Nov 2026, 00:01 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 26.04.2
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  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), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade scripta/escriptorium to 26.04.2.

Affected software

ProductAffectedFixed in
ScriptaeScriptoriumAffected
  • <=26.4.1
Fixed in–
GitHubscripta/escriptoriumpkg:github/scripta/escriptoriumOther threatsAffected
  • <26.04.2
Fixed in
  • 26.04.2

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

AI-suggested

If you cannot patch yet, restrict access to trusted authenticated users only and monitor for suspicious access control changes. Avoid using affected versions prior to 26.04.2 in sensitive environments if possible.

Description

CVE-2026-18277 is a missing authorization vulnerability in Scripta eScriptorium versions prior to 26.04.2. It allows a remote authenticated user to grant themselves access to another user's private OCR model and revoke access for any user via POST requests. The flaw exists because the ownership check is only performed during GET requests, not during POST operations that modify access.

References

Community reviews

Loading reviews…