Skip to main content
VulnerabilityPublished Updated

CVE-2026-1324: Sangfor Operation and Maintenance Management System · OS Command Injection

Affects Sangfor Operation and Maintenance Management SystemSource CVE Database V5

0

Not known to be exploited · CVSS 8.7 High.

Data as of 26 Oct 2026, 09:08 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
6.9% chance of exploitation in 30 days – higher than 94% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
SangforOperation and Maintenance Management SystemAffected
  • =3.0.0
  • =3.0.1
  • =3.0.2
  • =3.0.3
  • =3.0.4
  • =3.0.5
  • =3.0.6
  • =3.0.7
  • =3.0.8
  • =3.0.9
  • =3.0.10
  • =3.0.11
  • =3.0.12
Fixed in–

AI-suggested

1. Immediate network-level mitigation: Restrict access to the Sangfor OMMS management interfaces to trusted IP addresses using firewalls or network segmentation to reduce exposure. 2. Deploy Web Application Firewalls (WAFs) or Intrusion Prevention Systems (IPS) with custom rules to detect and block suspicious payloads targeting the 'keypassword' parameter. 3. Monitor logs for unusual command execution patterns or unexpected SSH protocol handler activity indicative of exploitation attempts. 4. If possible, disable or isolate the vulnerable SSH Protocol Handler component until a vendor patch is available. 5. Conduct thorough vulnerability scanning and penetration testing to identify affected systems within the environment. 6. Engage with Sangfor support channels for updates or unofficial workarounds, and subscribe to threat intelligence feeds for emerging exploit information. 7. Implement strict privilege separation and run OMMS services with the least privileges necessary to limit the impact of potential exploitation. 8. Prepare incident response plans specifically addressing OS command injection scenarios to enable rapid containment and remediation. 9. Consider deploying application-layer sandboxing or containerization to limit the scope of command execution if feasible.

Description

A vulnerability was identified in Sangfor Operation and Maintenance Management System up to 3.0.12. Affected by this issue is the function SessionController of the file /isomp-protocol/protocol/session of the component SSH Protocol Handler. The manipulation of the argument keypassword leads to os command injection. It is possible to initiate the attack remotely. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.

References

Community reviews

Loading reviews…