vciy

CVE-2026-33815

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

CVE-2026-33815 in github.com/jackc/pgx

CVE-2026-338153 of 4 sources documented this
unranked

No rank

rank@v1 withholds a number for this record

nothing this rule scores is held for this record, so there is no ordering to state. That is a fact about the sources, not a finding about the software.

Hindsight · the state

0.00605EPSSNOT IN KEVas of 2026-09-20
Severitynot scored
Harmnot stated
Exploitationnone in held sources
Defensefix version namedreceipt
Movementdoubled within 72hreceipt
PLATEAU10Minimal movement since 2026-04-08, 83 days at 0.01, as of 2026-06-30. arc-rules@v1

Foresight · where to check next

No weakness class or product neighbourhood is held for this record, so this index cannot name anywhere to check next. That is an absence in the record, not a finding about the software.

Color is a claim, not decoration:the hostile worldthe defenseno signal

Sources disagree here.

Weakness class
GoCWE-129 — Improper Validation of Array Indexreceipt
NVDCWE-787receipt

Both shown, dated. We don't pick winners. disagreement-rules@v1

Running github.com/jackc/pgx/v5/pgproto3? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

ReachNo CVSS vector in held sources, so no reach or impact can be stated.
Weakness classCWE-129 Improper Validation of Array Indexreceipt
Published consequencesCWE-129: Integrity, Availability: DoS: Crash, Exit, or Restart; Integrity: Modify Memory; Confidentiality, Integrity: Modify Memory, Read Memory…[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

Fixed in5.9.0receipt
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.

Exploit Status & Known PoCs a ladder, not a score

Current rung: Nothing observed in held sources.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

Exploit probability0.00605 · top 52% of all CVEsreceipt
Assigned byGoreceipt
Recorded changes9 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productgithub.com/jackc/pgx/v5/pgproto3receipt
Fixed in5.9.0receipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

Memory-safety vulnerability in github.com/jackc/pgx/v5. receipt

NVD's analysis a second authority

weakness
CWE-787
also scored by
9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H · 8.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L

The CNA and NVD map this to different weakness classes. Both are shown because both were published; we do not pick one.

check it yourself pkg.go.dev receipt

Movement the material steps

8 Apr 20260.00018
15 Jun 20260.004 · scoring model v2026.06.15
30 Jun 20260.00605

This score more than doubled inside 72 hours. Both observations are in the full history below.

Show all 9 observations
8 Apr 20260.00018
10 Apr 20260.00043
13 Apr 20260.00056
9 May 20260.00061
22 May 20260.00022
14 Jun 20260.00023
15 Jun 20260.004
23 Jun 20260.00408
30 Jun 20260.00605

9 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.00605Published2026-04-07Index as of2026-06-30

Exploit probability more than doubled between 2026-04-08 and 2026-04-10 (0.00018 → 0.00043) and the record had been public for 2 months when this index was last written.

Published 2026-04-07 receipt · Index as of 2026-06-30 derived

Siblings and hubs

Records related to this one

Its defect family

github.com/jackc/pgx/v5/pgproto3

Of the 2 records in this family, this is the only one whose title names cve-2026-33815.

Grouped by shared product and weakness, not by shared vulnerability. Each record's own state is on its own page.

Family membership: held values

This record is one of a group, and the group's page describes all of them. This page is kept and dated, and the defect family's own page is the one we offer for indexing: the whole group.

Browse the index from here

These are index-wide views, not findings about CVE-2026-33815.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.