CVE-2026-95649I.R.I.S S.A. IRISPowerscan inclusion of untrusted functionality
CVE-2026-95649 is a inclusion of untrusted functionality in I.R.I.S S.A. IRISPowerscan, rated medium (6.1 on CVSS 4.0).
Why this priority: Medium severity, with no exploitation signal.
Published · Updated · NVD status: Received
What it is
The product loads code from a source outside its control.
How it is reached
An attacker can exploit it from the same local network segment, without an account, and nobody has to click anything. Success also depends on conditions the attacker does not fully control.
What an attacker gains
A successful attack can read the data it protects and take it offline. In practice, this kind of flaw lets an attacker run their code inside your build or your running service.
Is it being exploited?
There is no public report of exploitation yet. EPSS estimates a 0.14% chance of exploitation activity in the next 30 days, higher than 3% of scored CVEs.
What to do
- No fixed version is listed yet. Find every place I.R.I.S S.A. IRISPowerscan runs, watch the references for a fix, and plan a replacement if it is no longer supported.
- Segment the networks that can reach it.
Description from NVD
IRISPowerscan insufficiently restrict the use of untrusted scripts. An authenticated user with access to script functionality can import or modify scripts that are executed by the application, potentially resulting in arbitrary code execution in the security context of the Windows user running IRISPowerscan.
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- Build pipelines, dependencies and plugins. The flaw sits between third-party code and your build or runtime.
- Update channels. The flaw sits between third-party code and your build or runtime.
Trust boundaries in play
- Local network segment. The attacker must share a network segment with the target.
- Between third-party code and your build or runtime. An attacker who crosses it can run their code inside your build or your running service.
Questions to answer about your own systems
- Where does I.R.I.S S.A. IRISPowerscan run in your systems, and at which version?
- Which network segments can reach them?
- What can it reach once compromised: which data stores, secrets and services?
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.