justdoit0910 CVE Vulnerabilities & Metrics

Focus on justdoit0910 vulnerabilities and metrics.

Last updated: 15 Feb 2026, 23:25 UTC

About justdoit0910 Security Exposure

This page consolidates all known Common Vulnerabilities and Exposures (CVEs) associated with justdoit0910. 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 justdoit0910 CVEs: 1
Earliest CVE date: 20 Jan 2026, 16:16 UTC
Latest CVE date: 20 Jan 2026, 16:16 UTC

Latest CVE reference: CVE-2025-56353

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 justdoit0910 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 justdoit0910 CVEs

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

All CVEs for justdoit0910

CVE-2025-56353 justdoit0910 vulnerability CVSS: 0 20 Jan 2026, 16:16 UTC

In tinyMQTT commit 6226ade15bd4f97be2d196352e64dd10937c1962 (2024-02-18), a memory leak occurs due to the broker's failure to validate or reject malformed UTF-8 strings in topic filters. An attacker can exploit this by sending repeated subscription requests with arbitrarily large or invalid filter payloads. Each request causes memory to be allocated for the malformed topic filter, but the broker does not free the associated memory, leading to unbounded heap growth and potential denial of service under sustained attack.