Skip to main content
VulnerabilityPublished

CVE-2026-27897: WanderingAstronomer Vociferous · Path Traversal

Affects WanderingAstronomer VociferousSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 10.0 Critical : upgrade to 4.4.2 as a priority.

Data as of 30 Oct 2026, 11:52 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Mar 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 30 Oct 2026.

What to do

Upgrade Vociferous and wanderingastronomer/Vociferous to 4.4.2.

Affected software

ProductAffectedFixed in
WanderingAstronomerVociferousAffected
  • <4.4.2
Fixed in
  • 4.4.2
GitHubwanderingastronomer/Vociferouspkg:github/wanderingastronomer/VociferousOther threatsAffected
  • <4.4.2
Fixed in
  • 4.4.2

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

AI-suggested

  1. Upgrade Vociferous to version 4.4.2 or later, where this vulnerability is patched.
  2. If upgrading immediately is not possible, restrict network access to the export_file API endpoint by implementing firewall rules or network segmentation to limit exposure.
  3. Harden CORS policies by configuring app.py to allow only trusted origins instead of wildcard or localhost.
  4. Implement additional input validation and sanitization on the filename parameter to reject directory traversal sequences and enforce strict path constraints.
  5. Introduce authentication and authorization controls on the API endpoints to prevent unauthenticated access.
  6. Monitor logs for suspicious file write activities or unexpected API calls.
  7. Conduct regular security audits and penetration testing focused on API endpoints and file handling logic.
  8. Educate developers on secure coding practices related to file system access and API security.

Description

Vociferous provides cross-platform, offline speech-to-text with local AI refinement. Prior to 4.4.2, the vulnerability exists in src/api/system.py within the export_file route. The application accepts a JSON payload containing a filename and content. While the developer intended for a native UI dialog to handle the file path, the API does not validate the filename string before it is processed by the backends filesystem logic. Because the API is unauthenticated and the CORS configuration in app.py is overly permissive (allow_origins=["*"] or allowing localhost), an external attacker can bypass the UI entirely. By using directory traversal sequences (../), an attacker can force the app to write arbitrary data to any location accessible by the current user's permissions. This vulnerability is fixed in 4.4.2.

References

Community reviews

Loading reviews…