Habr•July 22, 2026•🇷🇺Translated from Russian

From Hundreds of Alerts to Proven Vulnerabilities: INFERA AI.SafeCode Unifies Seven Scanners into a Single DevSecOps Pipeline

INFERA AI.SafeCode addresses the growing crisis in Application Security where traditional integration of separate SAST, DAST, and SCA tools produces hundreds of critical alerts, up to 80 percent of which are false positives.

The rapid adoption of AI coding assistants such as GitHub Copilot, Cursor, and Claude has multiplied both development speed and the volume of insecure code, turning AppSec into a bottleneck when legacy processes remain unchanged.

INFERA AI.SafeCode unites seven specialized engines under a single DevSecOps and MLSecOps framework: real-time SAST in IDE and CI/CD, SCA for open-source components and transitive dependencies, Secrets scanning with validity verification, DAST for running applications, an AI Pentest agent that simulates manual testing in a sandbox, Code Fuzzing for crash vulnerabilities, and API Fuzzing covering REST, GraphQL, gRPC, and WebSocket interfaces.

Results are normalized and deduplicated into a unified risk registry that automatically assigns high and critical issues to developers together with explanations, proof-of-exploit evidence, and remediation guidance.

Cross-validation between engines replaces manual triage. When SAST identifies a potential SQL injection, the platform automatically builds a targeted fuzzing harness; Code Fuzzing then attempts exploitation and returns a conclusive stack trace only if a crash occurs. Similarly, DAST detects authorization flaws such as IDOR by comparing responses across roles, after which the AI Pentest agent constructs attack graphs up to twelve steps deep to determine whether the issue can escalate to remote code execution.

Security checks run continuously inside the IDE, highlighting problems before commit and offering concrete AutoFix patches. Integration with GitLab and GitHub posts comments and ready pull requests directly on affected lines, while vibe-coded AI output is validated to prevent hallucinated vulnerabilities from entering the codebase.

API Fuzzing exercises stateful scenarios including authentication flows, mass assignment, JWT bypass, and malformed payloads using specifications such as OpenAPI, GraphQL schema, and .proto files. SCA analysis links vulnerable dependencies to actual code paths, distinguishing reachable CVEs from unused libraries, which is especially critical for organizations subject to Russian critical infrastructure regulations.

Secrets detection distinguishes test tokens from valid production credentials by performing live verification, converting potential noise into immediate incidents that trigger key revocation and investigation.

A centralized project view aggregates repositories, scan histories, attack-surface data, and metrics such as MTTR and SLA violations. The attack-surface module visualizes subdomains, open ports, endpoints, and entry-to-sink chains, giving CISO, AppSec, and development teams a shared, real-time picture of organizational risk.

Self-hosted deployment supports strict enterprise access controls and allows import of internal vulnerability databases to meet requirements of FSTEC Order No. 117, Order No. 21, GOST R 56939-2024, and Federal Law No. 152.

By confirming vulnerabilities before blocking pipelines and by providing reproducible evidence rather than raw alerts, INFERA AI.SafeCode enables development velocity while preventing uncontrolled growth of technical and security debt.

Related articles

Habr•Vulnerabilities & Exploits

Ghost Assets in Vulnerability Management: How Identification, Merging and Asset History Eliminate Anomalies in MaxPatrol VM

Positive Technologies experts explain how infrastructure changes create duplicate, merged and phantom assets that distort vulnerability management. The article details three core mechanisms inside MaxPatrol VM: unique asset identification across scan sources, non-destructive merging of new and existing data, and full lifecycle history with configurable aging policies. It describes how the system distinguishes assets using prioritized keys such as system ID, FQDN, MAC address and VM ID, then applies recursive merging rules that respect multiple data sources. Policies allow teams to set freshness and obsolescence thresholds, automatically hiding assets after 90 days while preserving historical snapshots for PDQL queries. The piece also covers practical cloning and partial-scan scenarios that can produce misleading duplicates or lingering collections.

BoletimSec•Vulnerabilities & Exploits

GreyNoise Detects Active Exploitation Attempts of CVE-2021-36260 Against Hikvision Cameras

GreyNoise recorded exploitation attempts targeting CVE-2021-36260 in Hikvision cameras and recorders between September 21 and October 1. The vulnerability carries a CVSS score of 9.8 and allows unauthenticated remote command execution through insufficient input validation in the embedded web server. Attack traffic originated from four IP addresses, three routed through a commercial VPN in Lithuania and one from a Ukrainian residential network, with all targets located in Ukraine. Attackers leveraged a publicly available Nuclei template to probe devices, though GreyNoise confirmed only scanning activity and not successful compromises. The five-year-old flaw remains actively scanned despite an available firmware patch from Hikvision and a CISA advisory recommending immediate updates. Password changes provide no protection because the attack requires no authentication. Defenders are advised to apply firmware updates, remove devices from public internet exposure, and segment video surveillance networks from critical infrastructure.

Security NEXT•Vulnerabilities & Exploits

Splunk Enterprise Discloses 46 Vulnerabilities Including Critical Patroni Authentication Flaw

Splunk has published three security advisories detailing a total of 46 vulnerabilities affecting Splunk Enterprise and related components. Three of the issues were rated critical, with CVE-2026-76268 receiving a CVSS v3.1 base score of 9.8. The flaw resides in the Patroni REST API used for PostgreSQL cluster management within search head clusters, allowing unauthenticated remote attackers to execute arbitrary operating system commands. Another high-severity issue, CVE-2026-76266, enables local privilege escalation to root on Linux systems during package updates. The remaining vulnerabilities cover product code, internally identified problems, and third-party packages. Organizations are urged to apply the available patches promptly.

安全客•Vulnerabilities & Exploits

Smart Fish Tank Power Strip Server Breached, Killing Aquarium Fish During National Day Holiday

During China's National Day holiday, the cloud servers of Woda Technology's smart power strips for fish tanks were compromised by malicious hackers, causing widespread remote disconnections and power outages for user devices. The attack left heating rods, oxygen pumps, and circulation systems offline for hours, resulting in the deaths of koi, arowana, and other ornamental fish that users had maintained for years. Woda issued a public notice confirming the intrusion was not a product defect or user error but a deliberate network attack, and the company has since upgraded firewalls, added multi-layer cloud protections, deployed backup servers, and improved local offline logic to prevent future failures. The incident highlights a critical IoT design flaw where devices rely entirely on vendor cloud platforms for control, allowing attackers who breach the server to remotely manage household appliances at scale. Security experts note that the same architecture is used across smart speakers, locks, cameras, and other consumer devices, creating a broad attack surface with minimal updates or segmentation. Woda has reported the case to authorities and preserved logs for forensic investigation.