Skip to main content
CVE-2025-12278VulnerabilityPublished Updated

CVE-2025-12278: Azure Access Technology BLU-IC2 · Improper Input Validation

Affects Azure Access Technology BLU-IC2Source CVE Database V5

0

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
Azure Access Technology BLU-IC2Affected
  • =0
Fixed in–

AI-suggested

1. Monitor Azure Access Technology advisories closely and apply vendor patches immediately upon release to address the logout functionality flaw. 2. Implement additional session management controls such as forced session expiration, multi-factor authentication, and anomaly detection for session activity to reduce risk during the vulnerability window. 3. Conduct thorough testing of logout and session termination processes in affected environments to identify and remediate any session persistence issues. 4. Employ network-level controls like web application firewalls (WAFs) to detect and block suspicious requests targeting session management endpoints. 5. Increase logging and monitoring of authentication and session events to detect unusual patterns indicative of exploitation attempts. 6. Educate security and IT teams about the vulnerability specifics to ensure rapid incident response if exploitation is suspected. 7. Where possible, isolate or segment systems running BLU-IC2 and BLU-IC4 to limit potential lateral movement by attackers. 8. Review and tighten access control policies to minimize exposure of vulnerable components to untrusted networks.

Description

Logout Functionality not Working.This issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5.

References

Community reviews

Loading reviews…