All blog posts
Updates 3 min read

How Commonveil Addressed Its November Security Findings

Commonveil reviewed multiple Snyk findings, removed unused libraries and updated runtime and build security settings.

By Comutability Published Update from
Security review checklist with a protective shield and magnifying glass, illustrating assessed and fixed issues.

Project update: 13 November 2026. GitHub pull request #4: merged into GitHub source, not necessarily deployed. Commonveil has not been independently security audited.

Commonveil reviewed multiple Snyk findings, removed unused libraries and updated runtime and build security settings.

Why this matters

A good security response distinguishes an exploitable application problem from an unused or build-only dependency. The review removed unused packages, moved towards current Node 26 LTS images and documented a time-limited acceptance for a build-time issue. Risk acceptance is not the same as pretending a warning has vanished.

Detailed change record

The public engineering notes below describe what was implemented or proposed and the evidence recorded with the change. Historical instructions in the notes describe the pull request at the time it was raised.

Fixes the five Snyk findings sent on 13 November. Details and reasons are in docs/SECURITY_REVIEW.md under "Snyk findings, 13 November 2026".

| Finding | Fix | |---|---| | fflate memory exhaustion (high, no fixed version) | Removed jspdf, an unused template leftover that brought it in. | | leaflet XSS in bindPopup (medium, no fixed version) | Removed react-leaflet, also unused. | | node permission-model over-grant (medium) | Images and CI move to Node 26 LTS (26.12.1+). Not exploitable before this either: Node scopes it to 26.x and Commonveil never uses --permission. The updater now takes Node from the official Node image rather than Alpine's package. | | braces recursion (high, no fixed version) | Accepted in .snyk until 13 December, with the reason: build-time only (Tailwind 3), on this repository's own patterns, absent from the bundle and both images. | | nodemailer (high) | Already removed on 12 November; the finding is from an earlier scan. |

Needs a human decision

  • Accepting braces. Merging this accepts the risk for 30 days. Please confirm you agree with the reasoning, or tell me to remove the .snyk entry.
  • The Node 26 move hasn't been run here. The session couldn't fetch Node 26 or reach Docker Hub. The new Test workflow on this pull request runs the full checks on Node 26 and 24, builds both images, and checks the updater has Node 26.12+, Docker and Compose. Please don't merge unless it's green.

Checks run in the session

npm run verify on Node 22.23.4: 231 Commonveil tests and Secure Net's 31 pass, type check, lint and both builds. npm audit: 0 vulnerabilities. Browser bundle checked for braces: none.

Decisions and principles behind the work

Comutability is building towards privacy, user control and genuinely self-hostable software. That does not mean every proposal is already deployed. Cryptography and security improvements need qualified human review and meaningful tests before any strong safety promises are made.

What comes next

Recheck any temporary exception at expiry, run CI on the intended runtime and confirm the deployed images match the reviewed code.

Check the sources

Sources and further reading

Explore the evidence and original project records behind this article.