Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Skip to content
cve.new Create a CVE report
Check your stack
CVE-2026-118673medium4.1

KeePassXC: Out-of-bounds write in browser integration response encryption with oversized database responses

Impact

KeePassXC versions 2.3.0 to 2.7.9 have an out-of-bounds write weakness in browser integration response encryption. A local attacker with access to the IPC endpoint and a valid database association can trigger this issue. The impact is an out-of-bounds write before any response is delivered.

Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.

Affected packages

This source has no supported package-version data for matching. You can read the advisory here, but this record alone cannot power a dependency check.

Affected products

Vendor version evidence. Product records are separate from automatic dependency matching.

keepassxreboot · GitHub_M

keepassxc

1 range
GitHub_M version evidence

Compare with this publisher’s ranges. This does not inspect your installation.

affected

>= 2.3.0, < 2.8.0

unaffected

unknown

Other versions: unknown

Original source description

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.

Inside the record

Evidence available

Package identity · not supplied
Version evidence
Remediation guidance · not supplied
Weakness classification
Additional publishers · not supplied

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-118673

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Underlying weaknesses

The source’s classification of what caused the vulnerability.

CWE-787 ↗

CWE-787: Out-of-bounds Write

GitHub_M

Related →
Contributing organizations · 1
GitHub_M

Assigning organization

2026-10-29

What changed

Follow changes
No substantive changes have been recorded here yet. History starts when cve.new observes a change after tracking is enabled; earlier edits are not reconstructed.

Large field values are marked as truncated previews. Original source snapshots remain retained.

References

4 sources
github.com/keepassxreboot/keepassxc/security/advisories/GHSA-3448-gh8j-3227
Security advisoryGitHub_M
github.com/keepassxreboot/keepassxc/pull/13679
PatchGitHub_M
github.com/keepassxreboot/keepassxc/commit/80e68bb4e8b89e383dd96b1bf5de169ca61367aa
PatchGitHub_M
github.com/keepassxreboot/keepassxc/releases/tag/2.8.0
Release notesGitHub_M