Brickcom Cube/Dome/Bullet/Box 3.2.3.5.6 default credentials

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.5$0-$5k0.84

Summaryinfo

A vulnerability, which was classified as problematic, has been found in Brickcom Cube, Dome, Bullet and Box 3.2.3.5.6. This impacts an unknown function. The manipulation leads to default credentials. This vulnerability is documented as CVE-2026-50005. The attack needs to be performed locally. There is not any exploit available.

Detailsinfo

A vulnerability was found in Brickcom Cube, Dome, Bullet and Box 3.2.3.5.6. It has been rated as problematic. This issue affects an unknown functionality. The manipulation with an unknown input leads to a default credentials vulnerability. Using CWE to declare the problem leads to CWE-1392. The product uses default credentials (such as passwords or cryptographic keys) for potentially critical functionality. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

Brickcom cameras ship with default credentials that allows any unauthenticated remote attacker to silently access camera feeds.

It is possible to read the advisory at brickcom.com. The identification of this vulnerability is CVE-2026-50005 since 06/08/2026. The exploitation is known to be easy. Attacking locally is a requirement. The technical details are unknown and an exploit is not publicly available.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Vendor

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒

CVSSv3info

VulDB Meta Base Score: 6.5
VulDB Meta Temp Score: 6.5

VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍

CNA Base Score: 7.7
CNA Vector (icscert): 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Default credentials
CWE: CWE-1392
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: No

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔒

Timelineinfo

06/08/2026 CVE reserved
06/12/2026 +4 days Advisory disclosed
06/12/2026 +0 days VulDB entry created
06/12/2026 +0 days VulDB entry last update

Sourcesinfo

Advisory: brickcom.com
Status: Confirmed

CVE: CVE-2026-50005 (🔒)
GCVE (CVE): GCVE-0-2026-50005
GCVE (VulDB): GCVE-100-370511

Entryinfo

Created: 06/12/2026 06:23
Changes: 06/12/2026 06:23 (72)
Complete: 🔍
Cache ID: 216::103

Be aware that VulDB is the high quality source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!