CVE-2026-2235VulnerabilityPublished 9 Feb 2026

CVE-2026-2235: HGiga C&Cm@il package olln-base · SQL Injection

Affects HGiga C&Cm@il package olln-baseSource CVE Database V5

Not known to be exploited · CVSS 7.1 High : upgrade to 7.0-978 soon.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

7.1High

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

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

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

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

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: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within 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.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Feb 2026
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 HGiga C&Cm@il package olln-base to 7.0-978.

Affected software

Product	Affected	Fixed in
HGigaC&Cm@il package olln-base	Affected <7.0-978	Fixed in 7.0-978

AI-suggested

1. Immediately restrict access to the C&Cm@il package to trusted and authenticated users only, employing strong authentication mechanisms such as multi-factor authentication (MFA). 2. Implement strict input validation and parameterized queries or prepared statements within the application to prevent SQL Injection. 3. Monitor database logs and application behavior for unusual query patterns indicative of injection attempts. 4. Conduct regular security assessments and code reviews focusing on input handling in the affected component. 5. Isolate the mail system within segmented network zones to limit lateral movement if compromised. 6. Maintain up-to-date backups of critical data to enable recovery in case of compromise. 7. Engage with HGiga for updates or patches and apply them promptly once available. 8. Educate users and administrators about the risks of credential compromise and enforce strong password policies.

Description

CVE-2026-2235 is a high-severity SQL Injection vulnerability in the HGiga C&Cm@il package olln-base component. It allows authenticated remote attackers to inject arbitrary SQL commands, potentially exposing sensitive database contents. The vulnerability requires low privileges and no user interaction, making exploitation relatively straightforward once authenticated. Although no public exploits are currently known, the impact on confidentiality is high due to possible unauthorized data disclosure. The vulnerability affects version 0 of the product, with no patches currently available. European organizations using this software, especially in countries with higher adoption of HGiga products or critical communication infrastructure, face significant risk. Mitigation involves restricting access to authenticated users, implementing strict input validation, and monitoring database queries for anomalies. Countries with notable HGiga market presence and strategic communication sectors, such as Germany, France, and the UK, are most likely to be affected. Given the ease of exploitation and potential data exposure, this vulnerability demands prompt attention and remediation efforts.

Impact

For European organizations, the primary impact is unauthorized disclosure of sensitive data stored within the C&Cm@il package database, including potentially confidential communications and user credentials. This can lead to data breaches, regulatory non-compliance (e.g., GDPR violations), reputational damage, and potential lateral movement within networks if attackers leverage exposed data. Since the vulnerability requires authenticated access, insider threats or compromised credentials could facilitate exploitation. The high confidentiality impact combined with ease of exploitation makes this a significant risk for organizations relying on HGiga's mail solutions, particularly those handling sensitive or regulated information. The absence of known exploits reduces immediate risk but does not eliminate the threat, as attackers may develop exploits. The vulnerability could also serve as a foothold for further attacks, including privilege escalation or persistent access.

Summary

CVE-2026-2235 identifies a SQL Injection vulnerability categorized under CWE-89 within the HGiga C&Cm@il package olln-base. This vulnerability arises from improper neutralization of special elements in SQL commands, allowing attackers with authenticated access to inject arbitrary SQL statements. The flaw enables reading of database contents, compromising confidentiality without affecting integrity or availability directly. The CVSS 4.0 score of 7.1 reflects a high severity, with an attack vector of network, low attack complexity, no user interaction, and requiring privileges but no additional authentication barriers beyond that. The vulnerability affects version 0 of the product, and no patches or known exploits have been reported yet. The vulnerability's technical details indicate it is straightforward to exploit once an attacker gains authenticated access, potentially exposing sensitive user or system data stored in the backend database. The lack of patches increases the urgency for organizations to implement compensating controls. Given the nature of the product—a mail package—exploitation could lead to leakage of sensitive communications or credentials, posing significant risks to confidentiality and privacy.

CWE-89Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #2OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Parameterization
If available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated.
Architecture and Design · Operation · Environment Hardening
Run your code using the lowest privileges that are required to accomplish the necessary tasks. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment.
OWASP Cheat Sheets
Query Parameterization (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
XML Security (opens in a new tab)
XML External Entity Prevention (opens in a new tab)
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.4 (opens in a new tab)
V5.3.5 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
Command Line Execution through SQL Injection (opens in a new tab)
Object Relational Mapping Injection (opens in a new tab)
SQL Injection through SOAP Parameter Tampering (opens in a new tab)
Expanding Control over the Operating System from the Database (opens in a new tab)
SQL Injection (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 16 Feb 2026, 13:31 UTC

WeaknessesCWE-89

Technical details

References

Community reviews

Related threats