Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Active exploitation is not confirmed from current sources for CVE-2026-75002. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

No. CVE-2026-75002 is not listed in CISA KEV in the supplied enrichment data. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Is there a public exploit?

3 public PoC repositories reported; 0 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS, EDR process telemetry, host service logs where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2026-75002 using CVSS 7.1, EPSS 0%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Prioritize based on EPSS, PoC availability, and external exposure. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

highRemote Code Execpublic exploit

CVE-2026-75002

CVE-2026-75002 — In Roundcube Webmail before 1.6.18 and 1.7.x before 1.7.3, mail search and LITERAL+ byte-count desynchronization could lead to information…

In Roundcube Webmail before 1.6.18 and 1.7.x before 1.7.3, mail search and LITERAL+ byte-count desynchronization could lead to information disclosure or privilege escalation via IMAP command injection.

Published Aug 17, 2026Updated Aug 17, 2026Sources: NVD, roundcube (CNA), GitHub, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Exploit code

public exploit, none observed

EPSS

ahead of 0% of scored CVEs

Affects

roundcube

webmail

CVSS base

7.1

high

Remediation

The vendor's own words where we have them.

Upgrade webmail to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Prioritize based on EPSS, PoC availability, and external exposure.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
roundcube	webmail	—	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

Low

Confidentiality

High

Integrity

High

Scope

Unchanged

Attack Complexity

High

Attack Vector

Network

Privileges Req

Low

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
7.1	CVSS 3.1	high	1.6	5.5	MITRE (CNA)

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

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-77 · Improper Neutralization of Special Elements used in a Command ('Command Injection')

Execute Unauthorized Code or Commands

Mitigation: If at all possible, use library calls rather than external processes to recreate the desired functionality.

Weakness & attack patterns

CWE-77Command Injection

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-248 · Command InjectionCAPEC-40 · Manipulating Writeable Terminal DevicesCAPEC-15 · Command DelimitersCAPEC-136 · LDAP InjectionCAPEC-76 · Manipulating Web Input to File System CallsCAPEC-43 · Exploiting Multiple Input Interpretation LayersCAPEC-183 · IMAP/SMTP Command InjectionCAPEC-75 · Manipulating Writeable Configuration Files

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Prioritize edge telemetry for network-reachable webmail.
Monitor for scanner or exploit-pattern traffic after 3 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPSEDR process telemetryhost service logs

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 7.1 (AV:N)
Aug 17, 2026 · NVD
Initial · CVE published
Aug 17, 2026 · NVD
CVE published by mitre
Aug 17, 2026 · SOCRadar CTI

References

5 on the record

github.com/roundcube/roundcubemail/commit/404d43f1b0125319c3cf8c9e3df39074c0cb80ad
Exploit, Third Party Advisory
github.com/roundcube/roundcubemail/commit/73233abe581b3b31cefd00041c7086c40e1793ea
Exploit, Third Party Advisory
github.com/roundcube/roundcubemail/releases/tag/1.6.18
Exploit, Third Party Advisory
github.com/roundcube/roundcubemail/releases/tag/1.7.3
Exploit, Third Party Advisory
roundcube.net/news/2026/08/09/security-updates-1.6.18-and-1.7.3
Vendor Advisory

Elsewhere on this site

roundcubeevery CVE for this vendor
Remote Code Execsame class
CWE-77other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2026-75002 is In Roundcube Webmail before 1.6.18 and 1.7.x before 1.7.3, mail search and LITERAL+ byte-count desynchronization could lead to information…, a high vulnerability affecting webmail from roundcube. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-75002. Public exploit evidence is: 3 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 7.1 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.