CVE-2026-3669
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 · uneditedA security vulnerability has been detected in Freedom Factory dGEN1 up to 20260221. This impacts the function AlarmService of the component com.dgen.alarm. Such manipulation leads to improper authorization. The attack needs to be performed locally. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
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 · low confidenceVulnerability in Freedom Factory dGEN1 device (com.dgen.alarm component, AlarmService function) allows improper authorization bypass. This is a local attack requiring physical or local system access to the device. The alarm service's authorization mechanism can be bypassed, potentially allowing unauthorized control of alarm functions.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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 dGEN1 device presenceLocate and verify the Freedom Factory dGEN1 device in your environment through asset inventory, network scanning, or physical inspection of alarm system hardwareAffected if You have a Freedom Factory dGEN1 device deployed in your environment
-
Verify AlarmService component statusCheck if the com.dgen.alarm component (AlarmService) is running or enabled on the device. This may be accessible through device admin interfaces, service logs, or system configuration screensAffected if The AlarmService (com.dgen.alarm) is active or enabled on the device
-
Review alarm service authorization configurationExamine the authorization settings for the AlarmService function through device management console, configuration files, or API endpoints related to alarm controlAffected if Authorization controls for the alarm service are present but can be bypassed or are improperly implemented
-
Inspect for unauthorized alarm control access attemptsReview device logs, audit trails, or security event logs for suspicious local access patterns or unauthorized alarm function calls from local or physical access vectorsAffected if Logs show evidence of authorization bypass attempts or unauthorized alarm control access from local users or physical access points
You are affected if you have a Freedom Factory dGEN1 device with the AlarmService (com.dgen.alarm) component enabled, as the vulnerability allows local attackers with physical or system access to bypass the alarm service authorization mechanism.
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 dataSince the vendor did not respond to the disclosure and no patch exists, implement compensating controls such as restricting physical access to the device, network segmentation, and monitoring for unauthorized local access attempts. Consider reaching out to vendor through alternative channels or evaluating alternative products if alarm security is critical.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3669 — 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-3669 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