NEOMSA APIM 4.6.0 Eliminates All Critical and High Vulnerabilities Registered in FSTEC BDU
Neoflex has released NEOMSA APIM 4.6.0, an on-premise API management platform and API Gateway. The main focus of this version is raising the security posture of the product supply chain.
Within the secure development lifecycle (SSDLC), engineers created an SBOM in CycloneDX format, scanned all components and transitive dependencies for known vulnerabilities using Grype, and mapped results to the FSTEC BDU database. After updating vulnerable libraries, the number of registered findings dropped from 57 to 7, with no Critical or High issues remaining in the final build.
Product overview
NEOMSA APIM includes an API Gateway, lifecycle management, authentication and authorization supporting OAuth 2.0, JWT and mTLS, rate limiting, traffic analytics, and a Developer Portal. It works with OpenAPI contracts and deploys on customer infrastructure, including Kubernetes, without sending traffic or metadata to the vendor cloud.
Release verification process
The security check follows a single pipeline:
- Build the release candidate with a frozen set of components.
- Generate the CycloneDX SBOM.
- Scan with Grype against CVE and GHSA databases.
- Map findings to the current FSTEC BDU export and assign severity, risk, and remediation status.
- Apply the Security Gate: the build is blocked until all Critical and High FSTEC BDU entries are resolved.
Medium and Low findings are recorded but do not block release; they are tracked for subsequent dependency updates.
Results
Updates eliminated all 10 Critical and 24 High vulnerabilities. Medium findings fell from 19 to 7, and all 4 Low findings were removed. The final 4.6.0 build contains no Critical or High entries from the FSTEC BDU at the time of the report.
Customers receive a controlled, auditable component list, a consolidated security report, and documented evidence that the product passed a formal security gate before shipment.
Related articles
How Modern API Attacks Abuse Legitimate Functionality Instead of Exploiting Vulnerabilities
Traditional API incidents once centered on authorization errors, access control issues, SQL injections, and known vulnerability exploitation. Today, many attacks on APIs no longer require finding code flaws; attackers simply use documented methods, valid authorization, and correct parameters at unexpected scale or timing. NGENIX security teams observe three main behavioral patterns: Burst attacks that overload resource-heavy endpoints, Shortwave attacks that exploit race conditions through timed parallel requests, and Carpet Bombing that distributes activity across dozens of endpoints for reconnaissance or scalping. These techniques often bypass WAF because each individual request appears fully compliant with API specifications. Protection is shifting toward behavioral analysis, sliding-window rate limiting, and monitoring of overall client behavior rather than single-request signatures. Real-world cases include sudden catalog scraping during contests and mass reservation of airline seats without purchases, leading to degraded service for legitimate users.
Critical Vulnerabilities Patched in WHMCS Billing Software for Hosting Providers
WebPros International has disclosed two serious vulnerabilities in its WHMCS billing management platform used by hosting and cloud service providers. CVE-2026-67399 allows unauthenticated remote code execution through unsafe deserialization of untrusted data under specific conditions, potentially compromising the entire server environment and associated data. CVE-2026-67398 affects the 2CheckOut payment gateway module and stems from missing authorization checks, enabling attackers to retrieve sensitive customer information including names, addresses, emails, and phone numbers without authentication. HackerOne assigned CVSS v4.0 scores of 9.3 (Critical) to the first issue and 8.2 (High) to the second. WebPros released fixed versions WHMCS 9.0.8 and 8.13.7, and recommended disabling the 2CheckOut module as a temporary mitigation for the second flaw.
Cisco Releases Critical Patches for Exploited SQL Injection Flaw in Secure Email Gateway
Cisco Systems has issued security updates for Cisco Secure Email Gateway to address a critical SQL injection vulnerability tracked as CVE-2026-76461. The flaw stems from insufficient input validation during email parsing and allows unauthenticated remote attackers to execute arbitrary SQL commands. Successful exploitation can lead to root-level access on the underlying operating system, enabling full command execution. The vulnerability carries a CVSSv3.1 base score of 9.8 and is rated Critical. Cisco confirmed active exploitation of the issue in September 2026. Recommended fixes include upgrading to versions 16.5.0-780, 16.0.4-3021, or 15.5.5-0141, with strong preference given to the newest release.
Telegram Desktop HTML Export Flaw Allowed Stealthy JavaScript Injection into Chat History
Researchers at ExPatch identified a vulnerability in Telegram Desktop that enabled attackers to embed malicious JavaScript into exported HTML chat histories without user detection. The flaw stemmed from insufficient sanitization of button captions added by bots, allowing hidden scripts to execute when the HTML file was opened in a browser. Malicious messages could be forwarded into chats and remain dormant until export, potentially exfiltrating messages, sender names, and timestamps to attacker servers. The issue affected versions 4.15.1 through 6.9.3, with fixes released in beta 6.9.4 and stable version 7.0.1 on July 14. No in-the-wild exploitation was observed, though the attack required specific conditions including an unpatched export and JavaScript-enabled browser. Users are advised to re-export chats after updating or open old files with JavaScript disabled.