What is the official website of Inox Wind Ltd. ?

The official website of Inox Wind Ltd. is http://www.inoxwind.com.

What is Inox Wind Ltd.'s cybersecurity risk score?

Inox Wind Ltd. has an AI-generated cybersecurity risk score of 763 out of 1000, indicating a Fair security posture according to Rankiteo's assessment.

How many security incidents has Inox Wind Ltd. experienced?

According to Rankiteo, Inox Wind Ltd. currently holds 0 security badges, indicating that no recognized compliance certifications are currently verified for the organization.

Has Inox Wind Ltd. been affected by any supply chain cyber incidents ?

According to Rankiteo, Inox Wind Ltd. has not been affected by any supply chain cyber incidents, and no incident IDs are currently listed for the organization.

Does Inox Wind Ltd. have SOC 2 Type 1 certification ?

According to Rankiteo, Inox Wind Ltd. is not certified under SOC 2 Type 1.

Does Inox Wind Ltd. have SOC 2 Type 2 certification ?

According to Rankiteo, Inox Wind Ltd. does not hold a SOC 2 Type 2 certification.

Does Inox Wind Ltd. comply with GDPR ?

According to Rankiteo, Inox Wind Ltd. is not listed as GDPR compliant.

Does Inox Wind Ltd. have PCI DSS certification ?

According to Rankiteo, Inox Wind Ltd. does not currently maintain PCI DSS compliance.

Does Inox Wind Ltd. comply with HIPAA ?

According to Rankiteo, Inox Wind Ltd. is not compliant with HIPAA regulations.

Does Inox Wind Ltd. have ISO 27001 certification ?

According to Rankiteo,Inox Wind Ltd. is not certified under ISO 27001, indicating the absence of a formally recognized information security management framework.

Which industry does Inox Wind Ltd. operate in ?

Inox Wind Ltd. operates primarily in the Renewable Energy Semiconductor Manufacturing industry.

How many employees does Inox Wind Ltd. have ?

Inox Wind Ltd. employs approximately 1,086 people worldwide.

Does Inox Wind Ltd. own any subsidiaries ?

Inox Wind Ltd. presently has no subsidiaries across any sectors.

How many LinkedIn followers does Inox Wind Ltd. have ?

Inox Wind Ltd.'s official LinkedIn profile has approximately 46,098 followers.

What is the NAICS classification code for Inox Wind Ltd. ?

Inox Wind Ltd. is classified under the NAICS code 33441, which corresponds to Semiconductor and Other Electronic Component Manufacturing.

Does Inox Wind Ltd. have a Crunchbase profile ?

No, Inox Wind Ltd. does not have a profile on Crunchbase.

Does Inox Wind Ltd. have a LinkedIn profile ?

Yes, Inox Wind Ltd. maintains an official LinkedIn profile, which is actively utilized for branding and talent engagement, which can be accessed here: https://www.linkedin.com/company/inox-wind-limited.

How many cybersecurity incidents has Inox Wind Ltd. experienced ?

As of July 2, 2026, Rankiteo reports that Inox Wind Ltd. has not experienced any cybersecurity incidents.

How many peer or competitor companies does Inox Wind Ltd. have ?

Inox Wind Ltd. has an estimated 2,761 peer or competitor companies worldwide.

NEWRankiteo Cyber Underwriting Desktop - Score, price, and bind from your desktop

WindowsmacOSLinux

Download

Badge your company to reduce your risk score and your cyber insurance costs!

Link verified badges to your company page to build trust with insurers and customers.

Apply now and get your badge!

Internal validation & live display

Insurers and partners see a safer profile

Faster underwriting decisions

Trusted by insurers. Chosen by leaders.

Proud contributor to the Society of Actuaries.

IWL

Boost Score +25 with badge (5 left)

763

/1000

Fair

788

/1000

Fair

Inox Wind Ltd. Vendor Cyber Rating & Cyber Score

inoxwind.com

Add Your Compliance Badge

Inox Wind is India’s leading wind energy solutions provider, offering comprehensive services from concept to commissioning and Operations & Maintenance (O&M). As part of the US$10 billion INOXGFL Group, we are committed to delivering high-quality, reliable, and cost-competitive wind energy solutions to IPPs, Utilities, PSUs, and Corporate investors.

IWL A.I CyberSecurity Scoring

Scoring History

IWL

Inox Wind Ltd. CyberSecurity News & History

Past Incidents

Attack Types

Entity

Type

Severity

Impact

Seen

Blog Details

Supply Chain Source

Incident Details

View

No data available

Loading…

A.I.

IWL Company Scoring based on AI Models

Cyber Incidents Likelihood 3 - 6 - 9 months

Actual

Prediction

Incident Predictions locked

Access Monitoring Plan

A.I Risk Score Likelihood 3 - 6 - 9 months

Actual

Prediction A

Prediction B

Prediction C

Prediction D

A.I. Risk Score Predictions locked

Access Monitoring Plan

Loading…

Underwriter Stats for IWL

Incidents vs Renewable Energy Semiconductor Manufacturing Industry Avg (This Year)

No incidents recorded for Inox Wind Ltd. in 2026.

Incidents vs All-Companies Average (This Year)

No incidents recorded for Inox Wind Ltd. in 2026.

Incident Types IWL vs Renewable Energy Semiconductor Manufacturing Industry Avg (This Year)

No incidents recorded for Inox Wind Ltd. in 2026.

Incident History - IWL (X = Date, Y = Severity)

Loading…

SUBSIDIARY

Inox Wind Ltd. Subsidiaries

Parent Company

IWL

Renewable Energy Semiconductor Manufacturing

Website: http://www.inoxwind.com

Company Size: 1,001-5,000 employees

No subsidiary data available for this company.

Loading…

Inox Wind Ltd. Similar Companies

Siemens Gamesa

cb siemensgamesa.com

Siemens Gamesa is a global technology leader in the renewable energy industry - specifically in the development, manufacturing, installation and maintenance of wind turbines. Being a pioneer in renewables since the 1980s, we put our scale and entrepreneurial culture to work on driving the energy transition towards a sustainable world. We empower our customers, people, and partners to lead the future with green energy. Siemens Gamesa is a trademark licensed by Siemens AG.

Loading…

NEWS

Inox Wind Ltd. CyberSecurity News

Global CVEs (Not Company-Specific)

CVE-2026-55790

SUMMARY

Craft CMS is a content management system (CMS). In versions 5.0.0-RC1 through 5.9.22 and 4.0.0-RC1 through 4.17.15, an attacker with only a GitHub account can plant a JavaScript payload in a craftcms/cms issue title. When a Craft admin uses the CraftSupport widget’s "Give feedback" screen and types a search term that returns the poisoned issue, the payload executes in the admin’s control panel session. No control panel account or elevated privileges are required on the attacker’s side. This issue has been fixed in versions 4.17.16 and 5.9.23.

Published

Date2026-07-01

Updated

Date2026-07-01

RISK INFORMATION (Score: )

cvss4

Base Score: 7.4

Complexity: LOW

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Impact Score

Exploitability

REFERENCES

CVE-2026-50284

SUMMARY

Craft CMS is a content management system (CMS). In versions 5.0.0-RC1 through 5.9.21 and 4.0.0-RC1 through 4.17.14, theAssetsController::actionDeleteFolder() only requires the deleteAssets:<volume-uid> permission for the target folder. It never enforces deletePeerAssets:<volume-uid>, even though Assets::deleteFoldersByIds() cascades deletion to every descendant folder and every asset inside, regardless of the uploader's assigned privileges. A low-privilege user who has been granted folder-management rights on a shared volume can therefore destroy assets uploaded by other users (peer assets), bypassing the per-asset peer-permission check that the sibling actionDeleteAsset endpoint correctly applies. This issue has been fixed in versions 4.17.15 and 5.9.22.

Published

Date2026-07-01

Updated

Date2026-07-01

RISK INFORMATION (Score: )

cvss4

Base Score: 7.1

Complexity: LOW

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Impact Score

Exploitability

REFERENCES

CVE-2026-50283

SUMMARY

Craft CMS is a content management system (CMS). Versions 5.0.0-RC1 through 5.9.20, and 4.0.0-RC1 through 4.17.13 contain an authorization issue in the AssetsController::actionReplaceFile that can delete a source asset without source delete permission by supplying both assetId and sourceAssetId. AssetsController::actionReplaceFile() supports replacing a target asset file using another existing asset as the source. The action loads: assetId -> $assetToReplace and sourceAssetId -> $sourceAsset, then enforces replace permissions using ($assetToReplace ?: $sourceAsset). When both IDs are provided, this expression resolves to the target asset so no permission check is performed against the source asset volume. When both assets are present, Craft copies the source file into the target and then deletes the source asset. There is no deletion check for for the source asset. An authenticated user who can replace files in one volume can delete assets in another volume where they do not have delete permission, as long as they can obtain a sourceAssetId, leading to broken content references and data loss. This issue has been fixed in versions 4.17.14 and 5.9.21.

Published

Date2026-07-01

Updated

Date2026-07-01

RISK INFORMATION (Score: )

cvss4

Base Score: 5.3

Complexity: LOW

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Impact Score

Exploitability

REFERENCES

CVE-2026-14440

SUMMARY

Description: To issue and renew TLS certificates on behalf of customers, Cloudflare's Universal SSL feature automatically manages the CAA RRset for the customer's zone. This auto-managed RRset is permissive by design (e.g. 'issue "letsencrypt.org"' without parameters). On Universal SSL zones, Cloudflare's authoritative DNS serves this auto-managed RRset at query time, superseding any customer-configured CAA records on the zone. When a customer publishes a stricter CAA record using the RFC 8657 accounturi or validationmethods parameters, the Certificate Authority does not observe those parameters when evaluating the served RRset under RFC 8659. As a result, the RFC 8657 account-binding and validation-method-binding protections are not enforced end-to-end on Universal SSL zones. Successful exploitation could result in issuance of a browser-trusted TLS certificate to an attacker, enabling MITM against the affected domain. Exploitation is non-trivial in practice: an attacker would need to hold an ACME account at one of the Certificate Authorities in the served CAA RRset and to simultaneously satisfy domain control validation across the multiple geographically distinct Network Perspectives the CA relies on for Multi-Perspective Issuance Corroboration. Cloudflare prefixes are anycast-announced from hundreds of locations globally, raising the bar against single-vantage-point BGP hijacks. Any resulting misissuance of a browser-trusted certificate is subject to Certificate Transparency logging required by major browsers, and would be visible to CT monitoring. Mitigation: Customers requiring strict RFC 8657 enforcement need to disable Universal SSL on the affected zone. Universal SSL's automatic CAA management and customer-set RFC 8657 accounturi and validationmethods enforcement are mutually exclusive by the nature of the issue, so there is no in-product workaround that preserves both. Certificate Transparency monitoring is recommended for all customers as a general detection control. Credits: David Osipov (ORCID: https://orcid.org/0009-0005-2713-9242), independent researcher

Published

Date2026-07-01

Updated

Date2026-07-01

RISK INFORMATION (Score: )

cvss4

Base Score: 7.6

Complexity: HIGH

CVSS:4.0/AV:A/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Impact Score

Exploitability

REFERENCES

CVE-2026-14422

SUMMARY

Out of bounds read and write in Tint in Google Chrome prior to 150.0.7871.46 allowed a remote attacker to potentially perform out of bounds memory access via a crafted HTML page. (Chromium security severity: High)

Published

Date2026-07-01

Updated

Date2026-07-01

RISK INFORMATION (Score: )

Impact Score

Exploitability

REFERENCES

Loading…

API

Access Data Using Our API

Get company history

curl -i -X GET 'https://api.rankiteo.com/underwriter-getcompany-history?
linkedin_id=axa' -H 'apikey: YOUR_API_KEY_HERE'

Try It API Documentation Rapid

MEASURE

What Do We Measure ?

Incident

Finding

Grade

Digital Assets

Every week, Rankiteo analyzes billions of signals to give organizations a sharper, faster view of emerging risks. With deeper, more actionable intelligence at their fingertips, security teams can outpace threat actors, respond instantly to Zero-Day attacks, and dramatically shrink their risk exposure window.

These are some of the factors we use to calculate the overall score:

Network SecurityIdentify exposed access points, detect misconfigured SSL certificates, and uncover vulnerabilities across the network infrastructure.

SBOM (Software Bill of Materials)Gain visibility into the software components used within an organization to detect vulnerabilities, manage risk, and ensure supply chain security.

CMDB (Configuration Management Database)Monitor and manage all IT assets and their configurations to ensure accurate, real-time visibility across the company's technology environment.

Threat IntelligenceLeverage real-time insights on active threats, malware campaigns, and emerging vulnerabilities to proactively defend against evolving cyberattacks.

Rankiteo

By Rankiteo

★ ★ ★ ★ ★

View on G2.com

Rankiteo is a unified scoring and risk platform that analyzes billions of signals weekly to help organizations gain faster, more actionable insights into emerging threats. Empowering teams to outpace adversaries and reduce exposure.

View latest plans →View all security reports →

MILESTONEG

Users
Love Us

Loading…