fix: remediate September 2026 security findings - #9
Open
jmgasper wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary\n\n- update Node and all affected transitive dependency paths for the September 2026 advisory set\n- rebuild the production stage on Alpine 3.24 with dynamically linked nodejs-current and patched system OpenSSL\n- run the final image as an unprivileged UID and exclude npm/package tooling\n- document the supported runtime and container hardening\n\n## Security findings addressed\n\n- Dependabot alerts 5-7 and 10-15: find-my-way 9.7.0, js-yaml 5.2.2/4.3.1/3.15.1, valibot 1.4.2, fast-uri 3.1.5, deepmerge-ts 8.0.0, and safe brace-expansion variants\n- Code-scanning alerts 1-6: the same patched lockfile paths\n- current ECR image findings: Node 26.5.1, Alpine OpenSSL 3.5.8, and patched application dependencies\n\n## Validation\n\n- pnpm audit --audit-level=moderate: no known vulnerabilities\n- pnpm lint: passed\n- pnpm build: passed after generating the documented Prisma/external client build inputs\n- Jest: 15 suites passed, 1 skipped, and 1 failed; 121 tests passed, 3 skipped, and 2 failed\n- the same two forums-moderation integration failures were reproduced on untouched origin/develop (4 passed and 2 failed in that baseline suite)\n- production Docker build: passed\n- runtime inspection: UID 10001, Node 26.5.1, libssl/libcrypto 3.5.8 with dynamic linkage, npm absent\n- Trivy critical/high/medium image scan with unfixed findings ignored: zero findings\n\nECR verification artifact: forums-api-v6:september2026-security-cca7ef3, digest sha256:b46776a966d672b02decafb2d3ae6170a0b33e34e531481f30b695a9daaa027a.\n\nExisting deployed and retained image digests are unchanged; their historical findings remain until the patched image is deployed and old artifacts expire or are retired.\n\nAWS Inspector completed the verification artifact scan with ACTIVE/SUCCESSFUL status and zero active critical/high/medium findings.