CVE-2026-50245
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 · uneditedBrickcom cameras allow unauthenticated access to live snapshot images via the /ONVIF endpoint and no authentication is required to retrieve still images from the camera feed.
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 confidenceBrickcom cameras contain an information disclosure vulnerability where the /ONVIF endpoint permits unauthenticated access to live snapshot images. Attackers can retrieve still images from the camera feed without any credentials, potentially exposing sensitive monitored areas.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
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 Brickcom camera presenceScan the network for Brickcom camera IP addresses or use network discovery tools to locate ONVIF-compatible devices. Check device documentation or management interface for the Brickcom brand and model.Affected if The network contains Brickcom cameras
-
Verify /ONVIF endpoint accessibilitySend an HTTP GET request to the camera /ONVIF endpoint without any authentication headers. For example: curl -v http://<camera_ip>/ONVIF or http://<camera_ip>/onvif/snapshotAffected if The /ONVIF endpoint responds with HTTP 200 and returns data without requiring authentication
-
Confirm snapshot retrieval without credentialsAttempt to retrieve a snapshot image by accessing common paths such as /ONVIF/snapshot, /onvif/media/snapshot, or /snapshot.jpg. Check the response Content-Type header for image/* and verify if valid image data is returned.Affected if Snapshot images are returned without any authentication token, username, or password
-
Check ONVIF service authentication settingsAccess the camera web interface or ONVIF service configuration and examine user authentication settings for the ONVIF service. Look for options related to anonymous access or authentication requirements.Affected if Anonymous access is enabled or no authentication is required for the ONVIF service
-
Review network exposure of camera servicesExamine firewall rules and network segmentation to determine if the camera HTTP ports (typically 80, 8080) and ONVIF services are exposed to untrusted networks or the public internet.Affected if The camera /ONVIF endpoint is accessible from untrusted networks without network-level access controls
A system is affected if Brickcom cameras expose an accessible /ONVIF endpoint that returns snapshot images without requiring authentication.
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 dataRestrict network access to the /ONVIF endpoint using firewall rules or network segmentation. If available, apply vendor firmware updates. Implement IP allowlisting as an additional control.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-50245 — 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-2026-50245 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