bleon-ethical CVE Vulnerabilities & Metrics

Focus on bleon-ethical vulnerabilities and metrics.

Last updated: 08 Mar 2026, 23:25 UTC

About bleon-ethical Security Exposure

This page consolidates all known Common Vulnerabilities and Exposures (CVEs) associated with bleon-ethical. We track both calendar-based metrics (using fixed periods) and rolling metrics (using gliding windows) to give you a comprehensive view of security trends and risk evolution. Use these insights to assess risk and plan your patching strategy.

For a broader perspective on cybersecurity threats, explore the comprehensive list of CVEs by vendor and product. Stay updated on critical vulnerabilities affecting major software and hardware providers.

Global CVE Overview

Total bleon-ethical CVEs: 1
Earliest CVE date: 24 Feb 2026, 15:21 UTC
Latest CVE date: 24 Feb 2026, 15:21 UTC

Latest CVE reference: CVE-2026-27208

Rolling Stats

30-day Count (Rolling): 1
365-day Count (Rolling): 1

Calendar-based Variation

Calendar-based Variation compares a fixed calendar period (e.g., this month versus the same month last year), while Rolling Growth Rate uses a continuous window (e.g., last 30 days versus the previous 30 days) to capture trends independent of calendar boundaries.

Variations & Growth

Month Variation (Calendar): 0%
Year Variation (Calendar): 0%

Month Growth Rate (30-day Rolling): 0.0%
Year Growth Rate (365-day Rolling): 0.0%

Monthly CVE Trends (current vs previous Year)

Annual CVE Trends (Last 20 Years)

Critical bleon-ethical CVEs (CVSS ≥ 9) Over 20 Years

CVSS Stats

Average CVSS: 0.0

Max CVSS: 0

Critical CVEs (≥9): 0

CVSS Range vs. Count

Range Count
0.0-3.9 1
4.0-6.9 0
7.0-8.9 0
9.0-10.0 0

CVSS Distribution Chart

Top 5 Highest CVSS bleon-ethical CVEs

These are the five CVEs with the highest CVSS scores for bleon-ethical, sorted by severity first and recency.

All CVEs for bleon-ethical

CVE-2026-27208 bleon-ethical vulnerability CVSS: 0 24 Feb 2026, 15:21 UTC

bleon-ethical/api-gateway-deploy provides API gateway deployment. Version 1.0.0 is vulnerable to an attack chain involving OS Command Injection and Privilege Escalation. This allows an attacker to execute arbitrary commands with root privileges within the container, potentially leading to a container escape and unauthorized infrastructure modifications. This is fixed in version 1.0.1 by implementing strict input sanitization and secure delimiters in entrypoint.sh, enforcing a non-root user (appuser) in the Dockerfile, and establishing mandatory security quality gates.