FeedExploreAsk AIAlertsSavedProfile

Categories

AICybersecurityInfrastructureDatabaseTech Updates

Tech news that matters.

FeedExploreAskAlertsSavedProfile
Back to feed
Cybersecurity·High

OpenStack Flaw Lets Users Reprogram Others' Hardware

A technician in a data center inspects hardware inside an open server rack.

TL;DR: Two critical flaws in OpenStack Cyborg allow authenticated users to attack other tenants. Attackers can cause service disruptions or perform unauthorized actions, including reprogramming specialized hardware like FPGAs, posing a major infrastructure risk.

By Neeraj Dhiman·3h ago·1 min read·updated 59m ago
Source

Key facts

Category
Cybersecurity
Impact
High
Published
3h ago
Source
Ubuntu Security Notices

Full summary

Critical flaws in OpenStack Cyborg let authenticated users disrupt services or even reprogram other tenants' hardware accelerators, creating a significant infrastructure risk.

Two high-severity security vulnerabilities have been discovered in OpenStack Cyborg, the framework for managing hardware accelerators like FPGAs and GPUs. The first flaw (CVE-2026-40214) is in the Accelerator Request API, which failed to properly check project ownership. This oversight allows an authenticated user from one project, or tenant, to delete accelerator requests belonging to a completely different tenant. The second vulnerability stems from a dangerously permissive default security policy. This policy was configured to authorize any request that carried a valid authentication token, effectively ignoring the specific permissions that should be assigned to a user. This setup undermines the principle of least privilege, a cornerstone of secure multi-tenant architecture, by treating all authenticated users as if they have broad access to certain functions. These flaws create a direct path for users to interfere with the operations of others sharing the same cloud infrastructure.

The consequences for organizations using OpenStack are severe. The API flaw enables cross-tenant denial of service attacks, where one user could cripple critical, high-performance workloads for another. The permissive policy flaw is even more alarming, opening the door for unauthorized remote actions against the hardware itself. The security advisory explicitly warns that an attacker could reprogram Field-Programmable Gate Arrays (FPGAs). This means they could alter the hardware's core logic to steal sensitive data, cause permanent damage, or create a persistent backdoor. This represents a fundamental breach of the isolation expected in a cloud environment, turning a shared resource into a shared liability. This incident serves as a critical reminder for IT and security teams to conduct regular audits, avoid relying on default policies, and prioritize applying security patches to mitigate these immediate risks.

Why it matters

The vulnerabilities allow authenticated but low-privilege users to disrupt other tenants' services or even reprogram their hardware, breaking the fundamental security isolation of a multi-tenant cloud environment and posing a severe risk to data integrity and infrastructure stability.

Business impact

Businesses relying on OpenStack for accelerated computing could face service disruptions from denial-of-service attacks. More critically, the ability for an attacker to reprogram hardware could lead to data theft, persistent system compromise, and significant reputational damage.

⚡ Action needed

Update OpenStack Cyborg to the latest patched version to fix two critical security vulnerabilities.

Action checklist

  1. 1Identify all OpenStack deployments using the Cyborg component.
  2. 2Review the official security notice for specific patched package versions.
  3. 3Schedule and apply the necessary updates to your OpenStack environment.
  4. 4Verify that the patches have been successfully applied.
  5. 5Audit security policies to ensure they follow the principle of least privilege.

Tags

#vulnerability#cve#cloud security#fpga#openstack#cyborg

Related on Notifire

  • ResearchCritical CVEs of 2026
  • GlossaryCVE
  • ResearchSupply-chain security

✦ Notifire newsletter

Get more Cybersecurity intelligence

Join engineers getting Notifire’s verified tech briefings — short, sourced, and free. No spam, unsubscribe anytime.

The day's most important tech briefings. No spam, unsubscribe anytime.

Primary source: Ubuntu Security Notices

Part of our research on

  • Critical CVEs of 2026 →

Tech intelligence for engineering teams

Short, verified briefings on AI, cybersecurity, infrastructure, and data — with the analysis and action steps that matter. Every briefing is sourced, fact-checked, and bylined to a named editor.

[email protected]Story tips & corrections welcomeHow we report →

The Notifire briefing

Verified tech intelligence in your inbox — AI, security, infra, and data.

The day's most important tech briefings. No spam, unsubscribe anytime.

Sections

  • AI
  • Cybersecurity
  • Infrastructure
  • Database
  • Tech Updates
  • Web3 & Chains

Newsroom

  • About Notifire
  • Editorial team
  • Editorial standards
  • Methodology
  • AI disclosure
  • Corrections

Resources

  • Explore
  • Research hubs
  • Comparisons
  • Tech glossary
  • FAQ
  • Alerts & watchlists

Follow

  • RSS feed
© 2026 NotifirePrivacyTermsCorrections
An independent, AI-assisted publication. Built at </Alpheric>
IntelligenceLive panel
Live

Top trending

Last 24h

    Popular tags

    Add to watchlist

    +OpenAI+Claude+PostgreSQL+Kubernetes+Cloudflare+AWS+CVE Critical

    Notifire score

    0–100 priority signal — combines impact, freshness, trending velocity, and source credibility.

  1. Atom feed
  2. LinkedIn
  3. X / Twitter
  4. Facebook
  5. Instagram
  6. YouTube