Skip to main content
VulnerabilityPublished

CVE-2026-119284: joserfc · Compact JWS size guard allocates attacker-controlled segments before rejection

Affects weaviate-cliSource GCVE Database

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

Not known to be exploited · CVSS 6.9 Medium : upgrade to 3.4.2_1 when convenient.

Data as of 31 Oct 2026, 16:23 UTC

CVSS 4.0 base score
6.9Medium
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 4.06.9
Patch
Available – fixed in 3.4.2_1
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 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 weaviate-cli to 3.4.2_1.

Affected software

ProductAffectedFixed in
Homebrewweaviate-clipkg:brew/weaviate-cliOther threatsAffected
  • >=3.4.1 <3.4.2_1
Fixed in
  • 3.4.2_1

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

AI-suggested

A patch is available in joserfc version 3.4.2_1 that fixes this issue by validating the input length before splitting it into segments. Users should upgrade to version 3.4.2_1 or later to mitigate this vulnerability. No additional mitigation steps are required beyond applying the official fix.

Description

joserfc 1.7.4 has a vulnerability in its compact JWS size guard where it allocates attacker-controlled segments before rejecting oversized inputs. This occurs because the library calls bytes.split() on the input before validating its length, causing an additional payload-sized memory allocation. The flaw allows an attacker to cause excessive memory usage before the size limit triggers rejection. A fix is available in version 3.4.2_1.

References

Community reviews

Loading reviews…