VulnerabilityPublished 8 Mar 2026Updated 11 Mar 2026

CVE-2026-3750: ContiNew Admin · Server-Side Request Forgery

Affects ContiNew AdminSource CVE Database V5

Compare

Public exploit available · CVSS 5.1 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score

5.1Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: High
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

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

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, 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: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system 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 Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 8 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity 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

Affected software

Product	Affected	Fixed in
ContiNew Admin	Affected =4.0 =4.1 =4.2.0	Fixed in–
Maventop.continew/admin`pkg:maven/top.continew/admin`Other threats	Affected =4.0 =4.1 =4.2.0	Fixed in–

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

AI-suggested

Organizations should immediately audit their ContiNew Admin deployments to identify affected versions (4.0, 4.1, 4.2.0). In the absence of an official patch, mitigations include restricting network access to the ContiNew Admin server, especially limiting outbound requests to trusted destinations only. Implement network-level controls such as egress filtering and firewall rules to prevent unauthorized SSRF exploitation. Monitor logs for unusual outbound requests originating from the ContiNew Admin server. If possible, isolate the server within a segmented network zone to reduce potential lateral movement. Review and harden the Storage Management Module configuration to minimize exposure. Engage with the vendor for updates and consider alternative solutions if remediation is delayed. Additionally, apply runtime application self-protection (RASP) or web application firewall (WAF) rules to detect and block SSRF attack patterns targeting the vulnerable URI.create function.

Description

A security vulnerability has been detected in ContiNew Admin up to 4.2.0. This issue affects the function URI.create of the file continew-system/src/main/java/top/continew/admin/system/factory/S3ClientFactory.java of the component Storage Management Module. The manipulation leads to server-side request forgery. The attack is possible to be carried out remotely. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

The SSRF vulnerability in ContiNew Admin could allow attackers to cause the affected server to initiate unauthorized requests to internal or external systems. This can lead to information disclosure of internal network details, access to internal services not otherwise exposed, or use as a pivot point for further attacks. While the direct impact on confidentiality, integrity, and availability is rated low, the ability to interact with internal resources can facilitate more severe attacks such as data exfiltration, lateral movement, or denial of service against internal components. Organizations using ContiNew Admin in critical infrastructure or sensitive environments face increased risk, especially if the software is internet-facing or integrated with sensitive storage systems. The lack of vendor response and patch availability prolongs exposure and complicates risk management. Although no active exploits are currently known, the public disclosure increases the likelihood of future exploitation attempts.

Summary

CVE-2026-3750 is a server-side request forgery vulnerability identified in ContiNew Admin software versions 4.0, 4.1, and 4.2.0. The vulnerability resides in the URI.create method of the S3ClientFactory.java file within the Storage Management Module. This flaw allows an attacker to manipulate the URI creation process, causing the server to send crafted requests to arbitrary internal or external resources. SSRF vulnerabilities can be leveraged to access internal services, bypass firewalls, or perform reconnaissance within a protected network environment. The vulnerability is remotely exploitable without requiring authentication or user interaction, increasing its risk profile. The CVSS 4.0 vector indicates network attack vector (AV:N), low attack complexity (AC:L), no authentication required (AT:N), but with high privileges required (PR:H), and no user interaction (UI:N). The impact on confidentiality, integrity, and availability is low, suggesting limited direct damage but potential for indirect consequences. The vendor was contacted but has not responded or issued a patch, and no public exploits have been observed yet. This leaves organizations reliant on ContiNew Admin exposed to potential future attacks leveraging this SSRF flaw.

References

Community reviews

Loading reviews…