Critical

Inductive Automation Ignition

All CISA Advisories

Overview

Inductive Automation's Ignition platform has a serious vulnerability that allows any authenticated user to create projects, due to a misconfigured setting in versions 8.1.53 and earlier. This is classified as CVE-2026-77393 and has a CVSS score of 8.8, indicating a high-level risk. The issue stems from the 'Create Project Role(s)' setting being left blank, which means no role restrictions were enforced. Users are encouraged to upgrade to version 8.1.54 or later, where project creation is limited to Designer sessions, or to configure their current version to restrict project creation appropriately. This vulnerability poses risks in critical sectors such as manufacturing and energy, making it crucial for organizations using this software to address the issue promptly to prevent unauthorized project creation.

Key Takeaways

  • Affected Systems: Inductive Automation Ignition versions 8.1.53 and earlier; CVE-2026-77393.
  • Action Required: Upgrade to Inductive Automation Ignition version 8.
  • Timeline: Newly disclosed

Original Article Summary

View CSAF Summary Successful exploitation of this vulnerability could allow any authenticated user to create projects. The following versions of Inductive Automation Ignition are affected: Ignition <=8.1.53 (CVE-2026-77393) CVSS Vendor Equipment Vulnerabilities v3 8.8 Inductive Automation Inductive Automation Ignition Incorrect Default Permissions Background Critical Infrastructure Sectors: Critical Manufacturing, Energy, Information Technology Countries/Areas Deployed: Worldwide Company Headquarters Location: United States Vulnerabilities Expand All + CVE-2026-77393 In Ignition 8.1.53 and earlier, the Gateway "Create Project Role(s)" setting shipped blank, which permitted any authenticated user to create projects (if they can execute gateway scripts). Ignition 8.1.54 restricts project creation to Designer sessions and no longer relies on this setting. The 8.3 series is not affected. View CVE Details Affected Products Inductive Automation Ignition Vendor: Inductive Automation Product Version: Inductive Automation Ignition: <=8.1.53 Product Status: known_affected Remediations Mitigation Inductive Automation has determined that this issue is a default-value configuration, not a flaw in the access control itself. The security control enforces exactly what the "Create Project Role(s)" setting specifies; because the setting shipped blank, no role was required to create a project. Populating the setting fully closes the vulnerability. Mitigation Inductive Automation recommends users upgrade to 8.1.54 or later (or the latest 8.3 version), which restricts project creation to Designer sessions and no longer relies on this setting. Users who must remain on an earlier 8.1 version can fully remediate the issue by setting "Create Project Role(s)" to match their Designer Role. Once the setting is populated, only users holding that role can create projects. See Gateway General Security Settings. https://docs.inductiveautomation.com/docs/8.1/platform/security/gateway-general-security-settings#gateway-security-settings-table Mitigation For more information, see the publication at the Inductive Automation Trust Center. https://security.inductiveautomation.com/?tcuUid=34477620-731d-4b70-b22b-9450f9a659a3 Relevant CWE: CWE-276 Incorrect Default Permissions Metrics CVSS Version Base Score Base Severity Vector String 3.1 8.8 HIGH CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H 4.0 8.7 HIGH CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N Acknowledgments Christopher Lusk of North Echo Security Research reported this vulnerability to Inductive Automation. Elhussain Fathy (0xSphinx) independently reported this vulnerability and confirmed the fix. Inductive Automation reported this vulnerability to CISA. Legal Notice and Terms of Use This product is provided subject to this Notification (https://www.cisa.gov/notification) and this Privacy & Use policy (https://www.cisa.gov/privacy-policy). Recommended Practices CISA recommends users take defensive measures to minimize the risk of exploitation of this vulnerability. Minimize network exposure for all control system devices and/or systems, ensuring they are not accessible from the internet. Locate control system networks and remote devices behind firewalls and isolating them from business networks. When remote access is required, use more secure methods, such as virtual private networks (VPNs), recognizing VPNs may have vulnerabilities and should be updated to the most current version available. Also recognize VPN is only as secure as the connected devices. CISA reminds organizations to perform proper impact analysis and risk assessment prior to deploying defensive measures. CISA also provides a section for control systems security recommended practices on the ICS webpage on cisa.gov/ics. Several CISA products detailing cyber defense best practices are available for reading and download, including Improving Industrial Control Systems Cybersecurity with Defense-in-Depth Strategies. CISA encourages organizations to implement recommended cybersecurity strategies for proactive defense of ICS assets. Additional mitigation guidance and recommended practices are publicly available on the ICS webpage at cisa.gov/ics in the technical information paper, ICS-TIP-12-146-01B--Targeted Cyber Intrusion Detection and Mitigation Strategies. Organizations observing suspected malicious activity should follow established internal procedures and report findings to CISA for tracking and correlation against other incidents. CISA also recommends users take the following measures to protect themselves from social engineering attacks: Do not click web links or open attachments in unsolicited email messages. Refer to Recognizing and Avoiding Email Scams for more information on avoiding email scams. Refer to Avoiding Social Engineering and Phishing Attacks for more information on social engineering attacks. No known public exploitation specifically targeting this vulnerability has been reported to CISA at this time. Revision History Initial Release Date: 2026-09-03 Date Revision Summary 2026-09-03 1 Initial Republication of Inductive Automation Trust Center update. Legal Notice and Terms of Use

Impact

Inductive Automation Ignition versions 8.1.53 and earlier; CVE-2026-77393.

Exploitation Status

No active exploitation has been reported at this time. However, organizations should still apply patches promptly as proof-of-concept code may exist.

Timeline

Newly disclosed

Remediation

Upgrade to Inductive Automation Ignition version 8.1.54 or later. Alternatively, for users remaining on earlier versions, set the 'Create Project Role(s)' to match the Designer Role to restrict project creation access.

Additional Information

This threat intelligence is aggregated from trusted cybersecurity sources. For the most up-to-date information, technical details, and official vendor guidance, please refer to the original article linked below.

Related Topics: This incident relates to Phishing, CVE, Vulnerability, and 2 more.

Related Coverage

Leaked LiteLLM Master Key Let Attackers Steal GitHub Tokens and Hijack Release Pipeline

The Hacker News

LiteLLM has reported a serious security incident stemming from the accidental exposure of a master key in a public GitHub repository. This key, which was found in a configuration file committed on May 27, 2026, enabled an attacker to manipulate the release pipeline of the popular Python package. As a result, the attacker was able to push a malicious version of the software, potentially compromising users who downloaded it. This incident raises significant concerns about the security practices surrounding sensitive information in open-source projects, particularly how such keys are managed and stored. Developers and organizations using LiteLLM's tools should review their security protocols to prevent similar incidents in the future.

Oct 24, 2026

Researchers Push Over 2 Million Updates to Remotely Disable Popcorn Time Updater That Could Fuel a Botnet

The Hacker News

In a significant cybersecurity move, the Dutch security firm Eye Security has remotely pushed over 2 million updates to computers to disable a background updater associated with Time4Popcorn, a discontinued version of the Popcorn Time app known for streaming pirated content. This updater posed a potential risk as it could allow unauthorized users to take control of affected machines. The updates were carried out between November 2025 and March 2026, targeting devices that did not belong to the firm. The action underscores the ongoing risks linked to abandoned software and highlights the need for users to be cautious about outdated applications. This incident serves as a reminder of the vulnerabilities that can arise from using unsupported software, especially those associated with illegal activities.

Oct 24, 2026

CISA Flags Two Actively Exploited Critical Flaws in Collabora Online and Arista VeloCloud

The Hacker News

The U.S. Cybersecurity and Infrastructure Security Agency (CISA) has flagged two critical vulnerabilities that are actively being exploited. These vulnerabilities affect the Collabora Online Built-in CODE Server and the Arista VeloCloud Orchestrator (VCO). The first vulnerability, identified as CVE-2026-110447, carries a CVSS score of 9.2, indicating its severity. Organizations using these products need to take immediate action, as attackers are actively exploiting these flaws. Prompt remediation is essential to protect sensitive data and maintain system integrity.

Oct 24, 2026

Exposed to PHP2Shell? Cyber Experts Weigh in With Advice

darkreading

Recent vulnerabilities in PHP, known as PHP2Shell, have raised concerns among cybersecurity experts. These flaws pose risks to numerous web applications that rely on PHP, potentially allowing attackers to exploit these weaknesses for unauthorized access or data manipulation. Users and administrators of PHP-based systems are advised to assess their exposure and implement protective measures. Simply updating software may not suffice, as the vulnerabilities require careful evaluation and tailored remediation strategies. This situation underscores the need for vigilance in maintaining web application security and keeping software up to date.

Oct 23, 2026

Microsoft Teams to get AI-powered, context-aware phishing detection

BleepingComputer

Microsoft is set to enhance its Teams messaging platform with AI-driven phishing detection capabilities starting in early November 2026. This new feature aims to identify and flag potential phishing attempts within Teams messages, helping users avoid falling victim to scams. The integration of AI is expected to improve the accuracy of phishing detection by analyzing the context of messages. This is particularly important as phishing attacks continue to rise, targeting both individuals and organizations. By implementing this technology, Microsoft hopes to bolster security for its users and reduce the risk of data breaches associated with phishing.

Oct 23, 2026

Ruby Fixes Three Regex Engine Bugs Responsible for Four Critical GitLab RCE Flaws

The Hacker News

Ruby has released updates to versions 4.0.9, 3.4.12, and 3.3.13 to address three bugs in the Onigmo regular expression engine. These bugs are linked to four critical vulnerabilities that GitLab recently patched. The vulnerabilities could allow attackers to craft specific patterns that may corrupt memory during the compilation process, potentially enabling remote code execution on affected servers. This issue is particularly concerning for GitLab users, as it puts their systems at risk if the vulnerabilities are exploited. Users are encouraged to update to the latest Ruby versions to mitigate these risks.

Oct 23, 2026