Approved changes feed: RSS · Atom
cpe:2.3:a:keepassxreboot:keepassxc:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Keepassxreboot (bd61dc68-fc18-5607-a602-f50195f75068) |
|---|---|
| Product | Keepassxc (1984fe64-ef96-577a-b652-a788f361bba8) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-69150 |
vulnerable | 2026-11-03 10:18:07.057695 |
KeePassXC: Heap use-after-free in KeePass1 (KDB) importer via unpruned m_entryUuids map
KeePassXC is a cross-platform community-driven port of the Windows application KeePass Password Safe. Prior to 2.8.0-beta1, KeePass1 / KDB legacy import retains raw Entry pointers in m_entryUuids after deleting metastream entries. When a crafted, unlockable .kdb file contains an earlier metastream entry followed by a KPX_CUSTOM_ICONS_4 metastream that references the earlier UUID, parseCustomIcons4() calls Entry::setIcon through the stale pointer, causing a heap use-after-free with a controlled write and a reliable process crash. This issue is fixed in version 2.8.0-beta1.
Published: 2026-10-13T15:23:36.744Z
Updated: 2026-10-13T20:22:44.545Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-118673 |
vulnerable | 2026-11-03 10:17:04.228378 |
KeePassXC: Out-of-bounds write in browser integration response encryption with oversized database responses
KeePassXC is a cross-platform community-driven port of the Windows application KeePass Password Safe. From 2.3.0 until 2.8.0, KeePassXC browser integration encrypts authorized responses in src/browser/BrowserMessageBuilder.cpp using a fixed 1 MiB output vector even though Botan::Sodium::crypto_box_easy() writes the plaintext length plus crypto_box_MACBYTES. A browser-protocol client that can access the per-user IPC endpoint, has a valid database association, and causes an unlocked database to generate and encrypt a sufficiently large authorized response can trigger a sequential out-of-bounds write before any response is delivered. This issue is fixed in version 2.8.0.
Published: 2026-10-29T16:01:55.635Z
Updated: 2026-11-03T16:32:32.671Z Reference links |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.