mosaic/stack
1
0
Fork 0
Code Issues 10 Pull Requests Actions Packages Projects Releases 2 Wiki Activity

fix(security): Update Go stdlib in postgres image (Trivy scanner component) #181

New Issue
Closed
opened 2026-02-01 23:55:33 +00:00 by jason.woltje · 0 comments
jason.woltje commented 2026-02-01 23:55:33 +00:00
Owner
Copy Link

Summary

Trivy scan identified HIGH severity vulnerabilities in Go stdlib components within the postgres image.

Affected Package

Package Current Fixed CVEs
stdlib (Go) v1.24.6 1.24.12 or 1.25.6 CVE-2025-58183, CVE-2025-61726, CVE-2025-61728, CVE-2025-61729

Affected Images

  • mosaic/postgres

Investigation Needed

These vulnerabilities are in Go stdlib, which may be coming from:

  1. A Go-based tool included in the postgres image
  2. The Trivy scanner component itself
  3. A base image component

Remediation

  1. Check docker/postgres/Dockerfile for Go-based tools
  2. Update base image if available
  3. If from an embedded tool, update that tool
  4. Rebuild and push image
  5. Verify vulnerabilities are resolved in Harbor

Priority

HIGH - Production image with known vulnerabilities.

## Summary Trivy scan identified HIGH severity vulnerabilities in Go stdlib components within the postgres image. ## Affected Package | Package | Current | Fixed | CVEs | |---------|---------|-------|------| | stdlib (Go) | v1.24.6 | 1.24.12 or 1.25.6 | CVE-2025-58183, CVE-2025-61726, CVE-2025-61728, CVE-2025-61729 | ## Affected Images - mosaic/postgres ## Investigation Needed These vulnerabilities are in Go stdlib, which may be coming from: 1. A Go-based tool included in the postgres image 2. The Trivy scanner component itself 3. A base image component ## Remediation 1. Check docker/postgres/Dockerfile for Go-based tools 2. Update base image if available 3. If from an embedded tool, update that tool 4. Rebuild and push image 5. Verify vulnerabilities are resolved in Harbor ## Priority HIGH - Production image with known vulnerabilities.
jason.woltje added the security label 2026-02-01 23:55:33 +00:00
jason.woltje added this to the M4.2-Infrastructure (0.0.4) milestone 2026-02-01 23:57:13 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
ai
AI/LLM integration
 api
Backend/API work
 api
auth
Authentication
 database
database
Database/schema work
 devops
Docker/deployment
 docs
Documentation
 frontend
graph
knowledge-module
migration
Data migration
 orchestrator
Orchestrator service (apps/orchestrator/)
 p0
Critical priority
 p1
High priority
 p2
Medium priority
 p3
Low priority
 performance
Performance work
 phase-1
phase-2
phase-3
phase-4
phase-5
plugin
MoltBot plugin work
 search
security
Security-related
 setup
Initial setup
 testing
Testing/QA
 web
Frontend work
No Label security
Milestone
No items
No Milestone M4.2-Infrastructure (0.0.4)
Projects
Clear projects
No project
Assignees
Clear assignees
jason.woltje
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaic/stack#181
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?