CVE-2026-4967: Remote Denial of Service in IMS via Out-of-Bounds Read
CVE-2026-4967 is a remote denial-of-service vulnerability in IMS caused by missing bounds validation during memory read operations. An attacker can remotely trigger an out-of-bounds read without authentication, causing the service to crash or become unavailable. The flaw requires only network access and no special privileges to exploit.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 7.5 HIGH · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Weaknesses (CWE)
- —
- Affected products
- 0 configuration(s)
- Published / Modified
- 2026-07-03 / 2026-07-06
NVD description (verbatim)
In IMS, there is a possible out of bounds read due to a missing bounds check. This could lead to remote denial of service with no additional execution privileges needed.
1 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
The vulnerability stems from insufficient bounds checking in IMS's memory access logic. When processing attacker-controlled input, the application fails to validate array or buffer boundaries before executing read operations. This permits an out-of-bounds memory access that leads to application termination or undefined behavior. The CVSS 3.1 score of 7.5 (HIGH) reflects a network-exploitable flaw with high availability impact and no confidentiality or integrity consequences.
Business impact
This vulnerability can disrupt service availability for organizations relying on IMS. Denial-of-service attacks can interrupt critical workflows, degrade user experience, and potentially trigger cascading failures in dependent systems. Organizations may face operational downtime, incident response costs, and reputational impact if services are unavailable during business-critical periods.
Affected systems
The vulnerability affects IMS installations. Specific product versions, vendors, and configurations are not detailed in available advisories. Organizations deploying IMS should verify their version against vendor security bulletins and determine exposure based on network accessibility of their IMS instances.
Exploitability
The vulnerability is highly exploitable. It requires only network access (AV:N), no authentication (PR:N), no user interaction (UI:N), and can be triggered from a single request (AC:L). An attacker with basic network connectivity can immediately craft malicious input to cause denial of service, making this a straightforward attack vector requiring minimal sophistication.
Remediation
Apply vendor-provided patches immediately upon availability. Until patching is complete, implement network-level controls to restrict access to IMS services—limit exposure to trusted networks, deploy rate limiting, and monitor for suspicious traffic patterns. Verify patch deployment across all IMS instances in your environment.
Patch guidance
Contact your IMS vendor or check their security advisory portal for available patches. Apply patches during a maintenance window to ensure service continuity. Test patches in a non-production environment first to validate compatibility with your deployment. Confirm patch installation by checking version numbers and conducting functional testing. Document the patch date and version for audit purposes.
Detection guidance
Monitor for repeated failed requests or crashes of IMS processes, particularly those triggered by unusual or malformed input. Implement network intrusion detection rules to identify suspicious traffic patterns targeting IMS ports. Log all IMS API calls and review for attempts to access invalid memory ranges or trigger error conditions. Alert on unexpected IMS service restarts or high CPU spikes during processing.
Why prioritize this
This vulnerability merits prompt patching due to its HIGH CVSS score, network-exploitable nature, and lack of authentication barriers. Denial-of-service impact directly affects business continuity. The absence of KEV listing does not reduce severity; organizations should patch based on CVSS score and exploitability metrics.
Risk score, explained
The CVSS 3.1 score of 7.5 reflects a high-severity flaw: remote attack vector (AV:N), low attack complexity (AC:L), no privilege or user interaction required (PR:N, UI:N), and high availability impact (A:H). No confidentiality or integrity loss (C:N, I:N) moderates the score slightly, but the ease of exploitation and guaranteed service disruption justify the HIGH rating.
Frequently asked questions
Can this vulnerability be exploited from the internet without credentials?
Yes. The vulnerability is network-accessible (AV:N), requires no authentication (PR:N), and no user interaction (UI:N). Any attacker with network access to an exposed IMS instance can trigger the denial of service remotely.
Does this vulnerability allow attackers to steal data or modify information?
No. The CVSS vector shows no confidentiality (C:N) or integrity (I:N) impact. This is purely an availability issue—attackers can crash the service but cannot read sensitive data or alter records.
How can we tell if we're running a vulnerable version of IMS?
Check your IMS version against your vendor's security advisory. The ground-truth data does not specify affected version ranges, so consult the vendor's bulletin or contact their support team directly to confirm whether your deployment is vulnerable.
Should we prioritize this even though it's not on the KEV list?
Yes. KEV listing is one indicator of active exploitation, but a 7.5 CVSS HIGH-severity, trivially exploitable vulnerability warrants immediate attention regardless of KEV status. Prioritize based on CVSS score, attack complexity, and business risk.
This analysis is based on publicly available vulnerability data as of the publication date. Affected product versions, patch availability, and vendor guidance were not specified in the source data—verify all remediation steps against official vendor advisories before implementing changes. SEC.co makes no warranty regarding the completeness or accuracy of vendor information. Organizations should conduct independent risk assessment based on their specific IMS deployment, network exposure, and business context. This assessment does not constitute professional security advice; consult qualified security professionals for your environment. Source: NVD (public-domain), retrieved 2026-08-11. Analysis generated by SEC.co (claude-haiku-4-5).
Related vulnerabilities
- CVE-2016-20062HIGHSQL Injection in Simply Poll 1.4.1 WordPress Plugin - Unauthenticated Data Theft
- CVE-2016-20063HIGHSQL Injection in Single Personal Message 1.0.3 – Credential & Data Theft Risk
- CVE-2016-20065HIGHUnauthenticated SQL Injection in Product Catalog 8 WordPress Plugin
- CVE-2016-20066HIGHWordPress CP Polls 1.0.8 Persistent XSS Vulnerability
- CVE-2016-20068HIGHUnauthenticated SQL Injection in WordPress Booking Calendar Contact Form 1.0.23
- CVE-2016-20069HIGHUnauthenticated SQL Injection in WordPress Booking Calendar Contact Form 1.0.23
- CVE-2016-20071HIGHCritical SQL Injection in WordPress 404 Redirection Manager Plugin v1.0
- CVE-2016-20072HIGHBBS e-Franchise WordPress Plugin SQL Injection – Remote Data Exfiltration Risk