← Incident database

voising-bi-2026 · Disclosed 2026-08-18

VOISING: unpatched BI tool data leakage

VOISING confirmed leakage of about 170,000 records via a BI vulnerability and reported that an available pre-intrusion patch had not been applied.

Known vulnerability

Outcome: Confirmed breach

Entry path and evidence

  • Reported fact

    A patch was available before unauthorized access but had not been applied.

    [s1]1. 調査結果【原因】 / 3. 本件不正アクセスへの対応と再発防止策【今後の対策】
  • Reported fact

    VOISING reported about 170,000 confirmed leaked records.

    [s1]1. 調査結果【漏えいが確認された件数および情報】

Timeline

  1. Incident disclosed. [s1]

Reported response

  • Reported fact

    VOISING reported stopping BI, discarding and rebuilding the environment, and revoking and rotating API keys and credentials.

    [s1]3. 本件不正アクセスへの対応と再発防止策【実施済みの対策】
  • Reported fact

    VOISING lists reduced direct exposure, data minimization, and patch deadlines and ownership as planned controls.

    [s1]3. 今後の対策

Cause and mitigation hypotheses

These are editorial hypotheses, separate from established causes and reported responses. Supporting and challenging observations are checks to investigate, not collected evidence.

  1. Mitigation hypothesis 1 Unverified

    Restricting BI exposure and checking deployed versions against patch deadlines could reduce exploitation opportunities while awaiting updates.

    Primary-source starting point

    VOISING reports delayed patching and plans to avoid direct Internet exposure.

    [s1]1. 原因 / 3. 今後の対策

    Read assumptions, observations, and limits
    Required assumptions
    • A relevant fix exists and access controls can restrict the attacker’s reachable path.
    Observations that would support it
    • Route configuration, deployed versions, and patch records demonstrate timely fixes and restricted paths.
    Observations that would challenge it
    • Unexpected public paths, unapplied fixes, or ownerless and undated exceptions remain.
    Assessment limits
    • Product and CVE are undisclosed; do not guess them or treat network restriction as protection from internal compromise or other flaws.

    Related inspection rules

Read this incident’s AI-ready guide ↗

Evidence relevant to prevention

Patch information / update review

Compare deployed BI versions with advisories and verify patch ownership and deadlines; limit exposure and accessible data.

Editorial assessment; not a determination of liability. [s1]

Unknowns and AI involvement

AI involvementUnknown

The cited sources do not establish attacker use of AI; absence of evidence is not evidence of absence.

BI product and CVE are undisclosed; proximity to another incident does not establish a shared product or vulnerability.

Sources

  1. [s1] VOISING · Primary source

    不正アクセスによる情報流出に関するご報告(第4報) ↗

    Published 2026-09-30 · Reviewed 2026-10-10