Skip to main content
VulnerabilityPublished

CVE-2026-61854: jackh54 VoiceSentinel · Race Condition

Affects jackh54 VoiceSentinelSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.2 High : upgrade to 3.3.1 soon.

Data as of 30 Oct 2026, 19:03 UTC

CVSS 3.1 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.18.2
Patch
Available – fixed in 3.3.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Oct 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 jackh54 VoiceSentinel to 3.3.1.

Affected software

ProductAffectedFixed in
jackh54VoiceSentinelAffected
  • >=2.2.1 <3.3.1
Fixed in
  • 3.3.1

AI-suggested

Upgrade VoiceSentinel to version 3.3.1 or later, where this race condition is fixed. If upgrading is not immediately possible, disable the optional report buffer feature (report_buffer.enabled set to false) to avoid exposure, as it is disabled by default.

Description

VoiceSentinel versions from 2.2.1 up to but not including 3.3.1 have a race condition in the optional report buffer feature. This race occurs between retention cleanup and transcript writes, leading to possible loss, duplication, or corruption of transcript data. The issue can also cause unbounded disk growth, potentially exhausting storage and crashing the host or other services. The feature is disabled by default and must be enabled to be affected. The vulnerability is fixed in version 3.3.1.

References

Community reviews

Loading reviews…