CVE-2025-45424VulnerabilityPublished 2 Jul 2025

CVE-2025-45424: Xinference · n/a

Affects XinferenceSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium : upgrade to 1.4.0 when convenient.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.4.0

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 2 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade honysyang/Xinference to 1.4.0.

Affected software

Product	Affected	Fixed in
GitHubhonysyang/Xinference`pkg:github/honysyang/Xinference`Other threats	Affected <1.4.0	Fixed in 1.4.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately assess their use of Xinference and determine if they are running versions prior to 1.4.0. Until a patch or update is available, organizations should restrict network access to the Xinference Web GUI interface by implementing strict firewall rules, allowing access only from trusted administrative IP addresses or VPNs. Network segmentation should be employed to isolate the Xinference management interface from general user networks and the internet. Monitoring and logging of access attempts to the Web GUI should be enhanced to detect any unauthorized access attempts promptly. Organizations should also review and update their incident response plans to include this vulnerability. Once the vendor releases a patched version (1.4.0 or later), organizations must prioritize upgrading to eliminate the vulnerability. If possible, disabling the Web GUI or replacing it with alternative management methods until patched can reduce risk. Additionally, organizations should conduct internal audits to verify no unauthorized changes or access occurred prior to mitigation. Employee awareness should be raised about this vulnerability to prevent social engineering attempts that could facilitate exploitation.

Description

Incorrect access control in Xinference before v1.4.0 allows attackers to access the Web GUI without authentication.

Impact

For European organizations using Xinference, this vulnerability poses a serious risk to operational security and data confidentiality. Unauthorized access to the Web GUI could allow attackers to extract sensitive information about AI models, configurations, or data processed by the platform. This could lead to intellectual property theft or exposure of personal data, potentially violating GDPR and other data protection regulations. Integrity of the system could be compromised if attackers modify configurations or deploy malicious models, impacting the reliability and trustworthiness of AI-driven decisions. Availability could also be affected if attackers disrupt the inference service, causing downtime or degraded performance. Given the increasing adoption of AI and machine learning platforms in Europe across sectors such as finance, healthcare, manufacturing, and government, exploitation of this vulnerability could have wide-reaching consequences. Additionally, the lack of authentication could facilitate lateral movement within networks if the Xinference instance is connected to internal systems. The absence of known exploits currently provides a window for mitigation, but the ease of exploitation (no authentication required) means that attackers with network access could quickly leverage this flaw once discovered.

CWE-284Improper Access Control (opens in a new tab)
Pillar weaknessCWE Top 25 (2025): #19OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Operation
Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
Third Party Javascript Management (opens in a new tab)
Virtual Patching (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V1.4.4 (opens in a new tab)
V1.4.5 (opens in a new tab)
V1.10.1 (opens in a new tab)
Attack patterns
Embedding Scripts within Scripts (opens in a new tab)
Modification of Windows Service Configuration (opens in a new tab)
Malicious Root Certificate (opens in a new tab)
Intent Spoof (opens in a new tab)
WebView Exposure (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 2 Jul 2025, 16:54 UTC

WeaknessesCWE-284

Technical details

References

Community reviews

Related threats