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
Zero-Day Vulnerabilities: The Invisible Threats Lurking in Modern Software
Zero-Day vulnerabilities represent one of the most challenging problems in cybersecurity because developers have no time to prepare defenses before exploitation begins. These flaws exist in software components without the knowledge of vendors, leaving antivirus tools and existing security mechanisms unable to detect attacks. Researchers discover such issues through techniques including fuzzing, reverse engineering, and static analysis. High-profile examples such as Heartbleed in OpenSSL, EternalBlue in Windows SMB, and Log4Shell in the Log4j library illustrate how single errors can affect millions of systems worldwide. Bug Bounty programs now allow companies to harness independent researchers to find problems before criminals exploit them. Organizations can reduce risk through regular updates, least-privilege principles, multi-factor authentication, and layered defenses, though complete elimination of zero-day risk remains impossible.
11-Year-Old Linux Kernel Race Condition NoisyTCP (CVE-2026-99288) Enables Remote DoS on Nginx, Apache and SSH Servers
Security researcher Hyunwoo Kim disclosed NoisyTCP (CVE-2026-99288), an 11-year-old race condition in the Linux kernel networking stack that allows unauthenticated remote attackers to trigger kernel panics and crash servers. The flaw stems from concurrent access to the ehash table during TCP socket lookup, where one CPU context may dereference a freed request_sock or full socket while another reuses the memory via SYN cookies. Exploitation requires multiple RX queues or RPS enabled and succeeds reliably on virtualized environments within seconds to minutes. Affected systems include nearly all distributions running kernels from 4.4 onward until the fix landed in November 2026. Temporary mitigations involve disabling SYN cookies or restricting traffic to a single RX queue, though both reduce resilience or performance. The researcher published full technical details on GitHub after coordinated disclosure.
Check Point Gateways Hit by PHP2Shell Exploits Installing TSGA Backdoor via Chained CVEs
An unidentified threat actor has been actively exploiting known vulnerabilities in unpatched Check Point Security Gateways to deploy the TSGA backdoor. The campaign began on 30 October 2026 against Israeli organizations and expanded on 2 November to targets across multiple countries and industries. Initial access leveraged CVE-2026-109618 and CVE-2026-109619 in exposed Mobile Access portals, followed by local privilege escalation through the previously unknown CVE-2026-123039 in Gaia OS. Attackers then installed PHP web shells and the TSGA backdoor, which provides encrypted remote access, configuration theft, persistence mechanisms, and log tampering via the embedded TSProxy component. In the first wave, operators pivoted to VMware ESXi hosts and deployed the destructive wiper destroy_v6. While tooling overlaps with the China-linked Armory Castle group’s PhiliKit framework, the use of a wiper and references to the Israel-Palestine conflict leave attribution open to three scenarios.
Apache Shiro Authentication Bypass Vulnerability Disclosed, Fixed in August Update
A critical authentication bypass vulnerability has been identified in the Java security framework Apache Shiro under specific LDAP caching configurations. The flaw, tracked as CVE-2026-129349, affects versions prior to 3.0.0 and carries a CVSSv4.0 base score of 9.1, rated Critical. Once a valid user authenticates successfully, subsequent login attempts using the cache accept any password for that username, enabling impersonation attacks. The Apache Shiro development team disclosed the issue on November 14, 2026, noting that the vulnerability was already resolved in version 3.0.1 released in August 2026. Version 3.0.2 was made available on November 8, 2026, and users are urged to upgrade immediately to the latest release.