PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-101036 FLB-Music CVE debrief

A vulnerability was found in FLB-Music FLB-Music-Player versions 1.1.8, 1.1.9, 1.2.0, and 1.2.1. The issue is in the path.join function in the /src/main/core/createParsedTrack.ts file, which is vulnerable to path traversal attacks. The attack requires local access. The exploit has been publicly disclosed, and the vendor did not respond to early disclosure.

Vendor
FLB-Music
Product
FLB-Music-Player
CVSS
LOW 1.9
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-28
Original CVE updated
2026-09-28
Advisory published
2026-09-28
Advisory updated
2026-09-28

Who should care

Defenders responsible for local deployments of FLB-Music FLB-Music-Player should assess the risk of path traversal attacks and prioritize verifying the presence of this vulnerability in their environment.

Why it matters

Defenders should prioritize verifying the presence of this vulnerability in their local deployments and assess the risk of path traversal attacks. The exploit has been publicly disclosed, and the vendor did not respond to early disclosure.

  • Verify the presence of vulnerable FLB-Music FLB-Music-Player versions in local deployments.
  • Assess the risk of path traversal attacks in the environment.
  • Apply patches or mitigations if available to prevent exploitation.

Technical summary

The vulnerability is in the path.join function in the /src/main/core/createParsedTrack.ts file of FLB-Music FLB-Music-Player versions 1.1.8, 1.1.9, 1.2.0, and 1.2.1. The issue allows for path traversal attacks, which require local access. This vulnerability impacts local deployments of FLB-Music FLB-Music-Player, allowing attackers to traverse paths. Defenders should prioritize verifying the presence of this vulnerability in their local deployments and assess the risk of path traversal attacks. The exploit has been publicly disclosed, and the vendor did not respond to early disclosure.

Defensive priority

Defenders should prioritize verifying the presence of this vulnerability in their local deployments and assess the risk of path traversal attacks.

Recommended defensive actions

  • Verify the presence of FLB-Music FLB-Music-Player versions 1.1.8, 1.1.9, 1.2.0, and 1.2.1 in your local deployments.
  • Assess the risk of path traversal attacks in your environment.
  • Consider applying patches or mitigations if available.
  • Review compensating controls for exposed systems while remediation is scheduled and verified.
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review.
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented.
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The CVE record and NVD entry provide details about the vulnerability, but the vendor did not respond to early disclosure. The exploit has been publicly disclosed. Defenders should verify the presence of vulnerable FLB-Music FLB-Music-Player versions in their local deployments and assess the risk of path traversal attacks. Limited source detail is available, so defenders should exercise caution and consider additional verification steps.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-101036 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-101036

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-101036 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-101036

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.