Rebuild and publish postgres-meta to patch Node.js Brotli vulnerability (CVE-2026-111497)
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 73/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- docker, node.js, typescript
Research direction
Start by locating the Docker build and release configuration for the meta image, then check how its Node.js version is selected. Rebuild and publish the image with Node.js 22.23.4 or later; verify it with the issue’s Docker command and confirm it reports the patched runtime.
Written by the indexing model from the issue text.
Description
Bug report
- I confirm this is a bug with Supabase, not with my own application.
- I confirm I have searched the Docs, GitHub Discussions, and Discord.
Describe the bug
The latest docker image supabase/postgres-meta:v0.100.0 (which is used by self-hosted/v0.8.3) is built prior to the October 21, 2026 Node.js security patch for CVE-2026-111497 (Critical CVSS 9.2 Brotli libbrotlidec out-of-bounds heap write / RCE affecting Node.js < 22.23.4 and < 24.22.1).
supabase/postgres-meta:v0.100.0 does not yet have a rebuilt image tag with Node.js 22.23.4.
To Reproduce
Steps to reproduce the behavior:
- Pull the latest image:
docker pull supabase/postgres-meta:v0.100.0
- Check the containers for the Node.js
CVE-2026-111497patch constant (zlib.constants.BROTLI_DECODER_ERROR_FORMAT_BLOCK_SWITCH === -17):
docker run --rm supabase/postgres-meta:v0.100.0 node -p "zlib.constants.BROTLI_DECODER_ERROR_FORMAT_BLOCK_SWITCH === -17 ? 'PATCHED' : 'VULNERABLE (' + process.version + ')'"
- See output confirming unpatched runtimes:
VULNERABLE (v22.23.3)
Expected behavior
- Rebuild and publish a new
supabase/postgres-metarelease using Node.js>= 22.23.4.
PATCHED (v22.23.4)
System information
- OS: Linux (Docker self-hosted)
- Version of Node.js inside containers:
supabase-meta(v0.100.0):v22.23.3
- Dominant language
- TypeScript
- Stars
- 1.3k
- Forks
- 228
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 3
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from supabase/postgres-meta
-
db.ts: init().end() resolves before the connection pool is closedPossibly taken @h-zahar claimed this 53 days ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
supabase/postgres-meta#1150 ·
Maintainers usually reply within 2 days
-
Relationship column lists are null for dotted/mixed-case schemasPossibly taken @hsusul claimed this 57 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
supabase/postgres-meta#1147 ·
Maintainers usually reply within 2 days
-
functions.create/retrieve fails for multi-word argument typesPossibly taken @hsusul claimed this 57 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
supabase/postgres-meta#1146 ·
Maintainers usually reply within 2 days
-
Column check introspection corrupts expressions with NOT VALID / NO INHERITPossibly taken @hsusul claimed this 58 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
supabase/postgres-meta#1143 ·
Maintainers usually reply within 2 days
-
Function create/update fails for config_params like statement_timeoutPossibly taken @hsusul claimed this 58 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
supabase/postgres-meta#1142 ·
Maintainers usually reply within 2 days
All issues in supabase/postgres-meta
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
oxidecomputer/skepsis#102 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
voidzero-dev/void#677 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
kunchenguid/gh-axi#247 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
lidge-jun/opencodex#8101 · 2 comments ·
Maintainers usually reply within 1 day