Skip to main content
VulnerabilityPublished

CVE-2026-124509: floci-io Floci · Path Traversal

Source GCVE Database

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

Public exploit available · CVSS 6.9 Medium · patch available : patch Floci as a priority.

Data as of 9 Nov 2026, 04:49 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 (VulDB)CVSS 4.06.9
CNA (VulDB)CVSS 3.17.3
CNA (VulDB)CVSS 3.07.3
CNA (VulDB)CVSS 2.07.5
Patch
Available
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Nov 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 8 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
floci-ioFlociAffected
  • =2.0
  • =2.1.0
Fixed in–
GitHubfloci-io/flocipkg:github/floci-io/flociOther threatsAffected
  • =2.0
  • =2.1.0
Fixed in–

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

AI-suggested

Upgrade floci-io Floci to version 2.2.0 or later to apply the official fix. This upgrade addresses the path traversal vulnerability in the S3Destination.bucketName function. No additional mitigation steps are indicated.

Description

A path traversal vulnerability exists in floci-io Floci versions up to 2.1.0 in the S3Destination.bucketName function of the S3 Destination Configuration Handler component. This vulnerability allows remote attackers to manipulate the BucketARN argument, potentially leading to unauthorized access or modification of files. The issue is fixed in version 2.2.0. Public exploit code is available, but there are no confirmed reports of exploitation in the wild.

References

Community reviews

Loading reviews…