Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-18265 – Unauthenticated Remote Code Execution – OSNEXUS QuantaStor 6.7.3.010+9c965a6414

Be the first to know when new zero-days emerge:

Summary

CVE-2026-18265 is a critical vulnerability in OSNEXUS QuantaStor, a software-defined storage management platform, that allows remote, unauthenticated attackers to execute arbitrary code with root privileges. The flaw resides in the configuration of Kapacitor, a component bundled with QuantaStor, and stems from a missing authentication check on functionality that should require credentials. The issue carries a CVSS v3.0 score of 9.8 (Critical) and requires no authentication or user interaction to exploit.

Technical details

  • Root cause: QuantaStor’s Kapacitor configuration lacks proper authentication controls on functionality that can be leveraged to achieve code execution (CWE-306: Missing Authentication for Critical Function).
  • Trigger conditions: An attacker needs only network access to the exposed QuantaStor/Kapacitor service; no valid credentials or user interaction are required.
  • Attack vector: Network (remote), low attack complexity, no privileges required, no user interaction.
  • Impact: Successful exploitation allows arbitrary code execution in the context of root, resulting in complete compromise of confidentiality, integrity, and availability of the affected storage system.

Affected software

  • OSNEXUS QuantaStor version 6.7.3.010+9c965a6414 (and earlier versions sharing the vulnerable Kapacitor configuration, per the vendor’s fixed-version guidance)

Severity

  • CVSS v3.0 Base Score: 9.8 (Critical)
  • Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade OSNEXUS QuantaStor to version 6.8.0 or later, which remediates this vulnerability.
  • If immediate patching is not possible:
    • Restrict network access to QuantaStor management interfaces and the Kapacitor service to trusted, internal networks only; do not expose these services directly to the internet.
    • Use firewall rules or network segmentation/VPN access to limit which hosts can reach the affected service.
    • Monitor QuantaStor systems for unexpected process execution or unauthorized configuration changes as an interim detective control until the patch can be applied.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge