CVE-2026-37579
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn issue in SMSGate sms-core<=2.1.13.6 allows a remote attacker to execute arbitrary code via the Cmpp7FDeliverRequestMessageCodec.java component
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceRemote code execution vulnerability in SMSGate sms-core version 2.1.13.6 and earlier, located in the Cmpp7FDeliverRequestMessageCodec.java component. The flaw allows a remote attacker to execute arbitrary code, likely through maliciously crafted CMPP protocol messages.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate sms-core installationSearch for sms-core JAR files or check application deployment directories for the sms-core component. Look for files named 'sms-core*.jar' or check your application dependency manifest for sms-core references.Affected if sms-core is present in the environment
-
Determine installed sms-core versionExamine the JAR file name, MANIFEST.MF file inside the sms-core JAR, or check the application's dependency management system (Maven pom.xml, Gradle build files, or application WAR/EAR metadata) for the sms-core version number.Affected if Version is 2.1.13.6 or earlier, or the version cannot be determined but sms-core is present
-
Identify Cmpp7FDeliverRequestMessageCodec componentSearch for the file Cmpp7FDeliverRequestMessageCodec.java or its compiled class (Cmpp7FDeliverRequestMessageCodec.class) within the sms-core JAR or application classpath. This is the vulnerable component.Affected if The Cmpp7FDeliverRequestMessageCodec component is found in the deployment
-
Verify CMPP protocol handling is enabledCheck application configuration files, startup scripts, or runtime settings for CMPP (China Mobile Peer-to-Peer Protocol) handler or receiver configurations. Look for CMPP-related beans, listeners, or protocol handler definitions.Affected if CMPP protocol processing is configured or active in the SMS gateway service
-
Assess network exposure of SMS gateway serviceReview firewall rules, network ACLs, and service binding configurations to determine if the SMS gateway (CMPP service port) is exposed to untrusted networks or external IP addresses.Affected if The SMS gateway service is accessible from untrusted networks or external hosts
The environment is affected if sms-core version 2.1.13.6 or earlier is installed, the Cmpp7FDeliverRequestMessageCodec component is present, CMPP protocol handling is enabled, and the service is network-accessible to potential attackers.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade sms-core to a version newer than 2.1.13.6. If immediate patching is not feasible, implement network segmentation and restrict external access to the SMS gateway service.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-37579 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-37579 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data