Security Resilience

CVE-2026-3066

Command Injection in Hummerrisk ≤ 1.5.0

Public PoCCommand Injection
Published
24 February 2026
Modified
24 February 2026
Patch / advisory
View advisory
CVSS Score v4 5.3
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.096 95th percentile
Risk Priority 45 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-3066 is a medium-severity Injection (CWE-74) vulnerability in Hummerrisk Hummerrisk. Its CVSS base score is 5.3 (Medium).

Operationally, ranked in the top 5% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-3066 is a command injection vulnerability affecting HummerRisk versions up to 1.5.0. The flaw resides in the fixedCommand function within the file hummer-common/hummer-common-core/src/main/java/com/hummer/common/core/utils/PlatformUtils.java, part of the Cloud Compliance Scanning component. It enables manipulation that leads to arbitrary command execution and is remotely exploitable.

Attackers with low privileges can exploit this vulnerability over the network with low complexity and no user interaction required. Successful exploitation grants limited impacts on confidentiality, integrity, and availability, as reflected in its CVSS v3.1 base score of 6.3 (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L). The issue maps to CWE-74 and CWE-77.

Advisories from VulDB and a GitHub issue in the AnalogyC0de/public_exp repository detail the vulnerability, including a publicly available exploit. The vendor was contacted early for disclosure but provided no response, and no patches or official mitigations have been issued.

Notable context includes the published exploit, which may already be in use, heightening risks for exposed HummerRisk deployments. The vulnerability was published on 2026-02-24.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

A flaw has been found in HummerRisk up to 1.5.0. This vulnerability affects the function fixedCommand of the file hummer-common/hummer-common-core/src/main/java/com/hummer/common/core/utils/PlatformUtils.java of the component Cloud Compliance Scanning. Executing a manipulation can lead to command injection. The attack can be executed remotely.…

more

The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

CWE(s)
CWE-74CWE-77

Related Threats

CVEs Like This One

CVE-2026-3064Same product: Hummerrisk Hummerrisk
CVE-2026-3065Same product: Hummerrisk Hummerrisk
CVE-2025-14276Shared CWE-74, CWE-77
CVE-2025-11335Shared CWE-74, CWE-77
CVE-2026-11451Shared CWE-74, CWE-77
CVE-2026-4468Shared CWE-74, CWE-77
CVE-2026-10878Shared CWE-74, CWE-77
CVE-2026-8777Shared CWE-74, CWE-77
CVE-2025-11098Shared CWE-74, CWE-77
CVE-2025-4747Shared CWE-74, CWE-77

Affected Assets

hummerrisk
hummerrisk
≤ 1.5.0

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover command-construction flaws before deployment.

SI-10 Information Input Validation good match

SI-10 directly requires validation of information inputs to reject malformed or special-element content before it reaches downstream parsers.

SA-8 Security and Privacy Engineering Principles partial match

Secure engineering principles include proper neutralization and safe command construction practices.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development catches injection vulnerabilities before release.

A.8.16 Monitoring activities partial match
finds

Monitoring activities can identify active injection attacks after they occur.

A.8.28 Secure coding partial match
prevents

Secure coding standards require proper neutralization of special elements, directly addressing CWE-74.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-74, a class-level weakness, and none of its children carries one either.
  • No fine-grained STIG row for CWE-77, a class-level weakness, and none of its children carries one either.

References