CVE-2021-26611
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedHejHome GKW-IC052 IP Camera contained a hard-coded credentials vulnerability. This issue allows remote attackers to operate the IP Camera.(reboot, factory reset, snapshot etc..)
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe HejHome GKW-IC052 IP Camera contains hard-coded credentials embedded in the firmware that allow unauthenticated remote attackers to gain administrative access. Attackers can execute privileged operations including device reboot, factory reset, and snapshot capture without any authentication.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 2.9.5= 2.9.6= 2.9.7= 4.0.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelCheck the device label, web interface, or documentation for the exact model number HejHome GKW-IC052Affected if Device is not a HejHome GKW-IC052 IP Camera (different models are not affected by this specific CVE)
-
Check the firmware versionAccess the camera web interface, navigate to System > Firmware/Version, or use the ONVIF or RTSP protocol to query device informationAffected if Firmware version is exactly 2.9.5, 2.9.6, 2.9.7, or 4.0.4
-
Verify network accessibilityAttempt to access the camera over HTTP/HTTPS from an external network or check firewall rules allowing inbound access to the camera portsAffected if Camera is directly accessible from untrusted networks (the hard-coded credentials can be exploited remotely)
-
Check for unauthenticated accessAttempt to access camera APIs or administrative endpoints without providing credentials to see if access is grantedAffected if Administrative functions (reboot, factory reset, snapshot capture) are accessible without authentication
The device is affected if it is a HejHome GKW-IC052 camera running firmware version 2.9.5, 2.9.6, 2.9.7, or 4.0.4 and is network-accessible to attackers.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataIf available, apply vendor firmware update to remove hard-coded credentials; otherwise isolate device behind firewall or replace with a patched device. Change default credentials if device supports credential modification.
- Consultation4.0 h
- Implementation6.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,064.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-26611 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-26611 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data