CVE Intelligence
Medium

CVE-2026-35504 — Subnet Solutions PowerSYSTEM Center CRLF injection

PowerSYSTEM Center email notification service is affected by a CRLF injection vulnerability when using SMTPS communication.

Published May 12, 2026 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: icscert

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.3% (30-day exploitation probability)+3
  • Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

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

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.31%
ahead of 22% of scored CVEs · Oct 14, 2026
Affects
Subnet Solutions
PowerSYSTEM Center 2020 and 2 more
CVSS base
5.5
Medium · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Subnet Solutions PowerSYSTEM Center 2020, Subnet Solutions PowerSYSTEM Center 2024, Subnet Solutions PowerSYSTEM Center 2026).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Subnet Solutions PowerSYSTEM Center 2020 ≤ 5.28.x Vulnerable CVE Program (cve.org) e CISA ADP
Subnet Solutions PowerSYSTEM Center 2024 ≥ 6.0.x and ≤ 6.1.x Vulnerable CVE Program (cve.org) e CISA ADP
Subnet Solutions PowerSYSTEM Center 2026 version 7.0.x Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

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

Attack vector
Adjacent
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

Every base score collected

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

ScoreVersionSeverityExpl.ImpactScored by
5.1 CVSS 4.0 Medium — — ics-cert@hq.dhs.gov via NIST National Vulnerability Database
5.1 CVSS 4.0 Medium — — icscert via CVE Program (cve.org) e CISA ADP
5.5 CVSS 3.1 Medium 2.1 3.4 ics-cert@hq.dhs.gov via NIST National Vulnerability Database
5.5 CVSS 3.1 Medium — — icscert via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L (score shown at the top: ics-cert@hq.dhs.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-93

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.31%

Detection

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

  • Not enough vector or weakness data: use the affected application’s logs as a starting point.
application logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · subnet solutions/powersystem center 2020, subnet solutions/powersystem center 2024, subnet solutions/powersystem center
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • CVSS changed · 5.5
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Awaiting Analysis
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVE published
    May 12, 2026 · icscert

Source activity

Repeated readings are counted rather than listed.

  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

2 on the record

Elsewhere on this site

Subnet Solutions
every CVE for this vendor
CWE-93
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-33570 Subnet Solutions PowerSYSTEM Center Incorrect Authorization May 12, 2026
  • CVE-2026-35555 Subnet Solutions PowerSYSTEM Center Incorrect Authorization May 12, 2026
  • CVE-2026-26289 Subnet Solutions PowerSYSTEM Center Incorrect Authorization May 12, 2026

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 fixed version, patch or mitigation documented.
  • 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 record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-35504 is "Subnet Solutions PowerSYSTEM Center CRLF injection", rated Medium. It affects PowerSYSTEM Center 2020 (Subnet Solutions); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.5 describes technical severity. EPSS 0.31% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.