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 August 29, 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,782 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-55867

SUMMARY

Graylog is a free and open log management platform. From 6.2.0 until 6.3.12, 7.0.7, and 7.1.2, the DELETE /users/{userId}/tokens/{idOrToken} endpoint implemented by UsersResource.revokeToken() in graylog2-server/src/main/java/org/graylog2/rest/resources/users/UsersResource.java checks USERS_TOKENREMOVE permission against the attacker-controlled userId path parameter before resolving the token selected by idOrToken. An authenticated user can provide an authorized userId while accessTokenService.loadById() or accessTokenService.load() resolves a token belonging to another user, including a service account or administrator, after which accessTokenService.destroy() deletes that token without checking AccessToken.getUserName(). The issue does not expose token contents, but unauthorized deletion causes integrity impact and can disrupt access-token-based integrations. This issue is fixed in versions 6.3.12, 7.0.7, and 7.1.2.

Published

Date2026-08-28

Updated

Date2026-08-28

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-55860

SUMMARY

MariaDB Connector/R2DBC is a non-blocking MariaDB and MySQL client implemented in Java. Prior to 1.4.1, org.mariadb:r2dbc-mariadb does not gate clear-text password authentication plugins on transport encryption because the AuthenticationPlugin interface has no capability for a plugin to require a secure connection. A hostile or man-in-the-middle MariaDB server can send an AuthSwitchRequest naming mysql_clear_password or dialog (PAM) over a plain-TCP unencrypted connection, and AuthenticationFlow permits ClearPasswordPluginFlow or PamPluginFlow to return the user's password as cleartext bytes on the wire. The disclosed credentials can subsequently be used to authenticate directly to the database server. This issue is fixed in version 1.4.1.

Published

Date2026-08-28

Updated

Date2026-08-28

RISK INFORMATION (Score: 5.9)

cvss3

Base Score: 5.9

Complexity: HIGH

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Impact Score

3.6

Exploitability

2.2

REFERENCES

CVE-2026-55859

SUMMARY

MariaDB Connector/R2DBC is a non-blocking MariaDB and MySQL client implemented in Java. Prior to 1.4.1, org.mariadb:r2dbc-mariadb encodes and decodes all character data under the assumption that the connection character set is UTF-8. A server can announce a mid-session change to character_set_client through the OK-packet session-state-tracking mechanism, including through SET NAMES executed by a stored routine or trigger, server configuration, or a hostile or man-in-the-middle server. If the new character set is not UTF-8, the driver continues to exchange UTF-8 while the server interprets the same bytes under a different encoding, causing silent data corruption and a client/server charset-confusion mismatch that can defeat byte-wise quoting or escaping. The fix accepts only utf8, utf8mb3, or utf8mb4 after initialization; any other value raises R2dbcNonTransientResourceException with SQLState 08000 and closes the connection. This issue is fixed in version 1.4.1.

Published

Date2026-08-28

Updated

Date2026-08-28

RISK INFORMATION (Score: 5.9)

cvss3

Base Score: 5.9

Complexity: HIGH

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

Impact Score

3.6

Exploitability

2.2

REFERENCES

CVE-2026-55858

SUMMARY

MariaDB Connector/J is used to connect applications developed in Java to MariaDB and MySQL databases. Prior to 2.7.14, 3.3.5, 3.4.3, and 3.5.9, the connector encodes and decodes protocol text and performs client-side escaping under the assumption that the connection character set is UTF-8. The server can report a mid-session change to character_set_client through OK-packet session-state tracking, including a change caused by SET NAMES, a stored routine or trigger, server configuration, or a hostile server. If character_set_client changes to a non-UTF-8 value, the driver continues to read and write UTF-8 while the server interprets the same bytes under another encoding, causing silent data corruption and a client/server charset-confusion mismatch that can defeat byte-wise quoting or escaping. The fix accepts only utf8, utf8mb3, or utf8mb4 after initialization; any other value causes SQLException with SQLState 08000 and closes the connection. This issue is fixed in versions 2.7.14, 3.3.5, 3.4.3, and 3.5.9.

Published

Date2026-08-28

Updated

Date2026-08-28

RISK INFORMATION (Score: 5.9)

cvss3

Base Score: 5.9

Complexity: HIGH

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

Impact Score

3.6

Exploitability

2.2

REFERENCES

CVE-2026-55857

SUMMARY

MariaDB Connector/J is used to connect applications developed in Java to MariaDB and MySQL databases. Prior to 2.7.14, 3.3.5, 3.4.3, and 3.5.9, PAM dialog authentication can be coerced into transmitting the account password over an insecure connection. The mysql_clear_password plugin is gated behind a secure transport, but the sibling PAM handler SendPamAuthPacketFactory, named dialog by the server, does not declare that requirement and inherits the default secure-required value false; older branches implement the same affected behavior in SendPamAuthPacket. A hostile or man-in-the-middle server can send an Authentication Switch Request for dialog over plain TCP, causing the driver to return the user's password in cleartext when sslMode=DISABLE and restrictedAuth=null, which is the default configuration. Properly verified TLS and local Unix sockets are not exposed to this transport vector. This issue is fixed in versions 2.7.14, 3.3.5, 3.4.3, and 3.5.9.

Published

Date2026-08-28

Updated

Date2026-08-28

RISK INFORMATION (Score: 5.9)

cvss3

Base Score: 5.9

Complexity: HIGH

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Impact Score

3.6

Exploitability

2.2

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…