Skip to content

chore: add newly disclosed PostgreSQL CVEs - #56

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
chore/pgdg-cve-scrape
Open

github-actions[bot] wants to merge 1 commit into
mainfrom
chore/pgdg-cve-scrape

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Automated PGDG security-index scrape.

The scraper (tools/scrape_pgdg.py) ran against
https://www.postgresql.org/support/security/?cve=title and
found CVE entries newer than what's in data/cves.json. The
proposed additions are in proposed-cves.json below.

Action items for a human:

  • Eyeball each entry: confirm it actually affects
    PostgreSQL 15-18.
  • Sanity-check summaries (one-line, technical).
  • Confirm CVSS thresholds (tool defaults to >= 7.0).
  • Merge the JSON into data/cves.json:
    bash uv run python tools/scrape_pgdg.py --write --yes uv run python tools/generate_cve_sql.py git add data/cves.json pgFirstAid.sql view_pgFirstAid.sql view_pgFirstAid_managed.sql git commit -m "chore: refresh CVE catalog"
  • Delete proposed-cves.json before merge.

@qodo-code-review

Copy link
Copy Markdown

PR Summary by Qodo

Propose newly scraped PostgreSQL CVEs for review

✨ Enhancement 🕐 40+ Minutes

Grey Divider

AI Description

• Stages 38 PGDG CVE candidates affecting PostgreSQL 15–18 with CVSS scores of at least 7.0.
• Keeps unverified entries out of the curated catalog and generated SQL pending human review.
• Requires merging approved entries and removing the proposal file before completion.
Diagram

graph TD
  A["PGDG security index"] --> B["PGDG scraper"] --> C["Proposed CVEs"] --> D{"Human approval"} -->|approved| E["Curated CVE catalog"] --> F["Generated SQL files"]
Loading
High-Level Assessment

The following are alternative approaches to this PR:

1. Write directly to the curated catalog
  • ➕ Produces catalog and generated SQL changes in one PR.
  • ➖ Makes unverified security metadata part of the deployable output before review.

Recommendation: Keep the review gate for scraped security data. Merge only after verifying the candidates, transferring approved entries to data/cves.json, regenerating SQL, and deleting the temporary proposal.

Files changed (1) +441 / -0

Enhancement (1) +441 / -0
proposed-cves.jsonStage 38 PostgreSQL CVE candidates +441/-0

Stage 38 PostgreSQL CVE candidates

• Adds scraped advisory IDs, CVSS scores, summaries, links, and per-major first patched minor versions for review. This file does not update the curated CVE catalog or generated SQL.

proposed-cves.json

@qodo-code-review

Copy link
Copy Markdown

Code Review by Qodo

🐞 Bugs (1)

Grey Divider


Action required

1. New database flaws go undetected 🔴 P0 🐞 Bug
Description
proposed-cves.json contains CVE-2026-116304 and other new entries, but neither the curated CVE
catalog nor the generated SQL incorporates them. If this PR merges as submitted, health checks using
the self-hosted function or managed view will not report those vulnerabilities.
Code

proposed-cves.json[R3-6]

+    "cve_id": "CVE-2026-116304",
+    "cvss": 8.8,
+    "summary": "PostgreSQL parallel RECORD typmod use-after-free executes arbitrary code",
+    "doc_link": "https://www.postgresql.org/support/security/CVE-2026-116304/",
Relevance

●● Moderate

PR explicitly stages proposed-cves.json for human review before merging into the catalog. No closely
matching accepted or rejected precedent. Only a recent dismissal on proposed-bugs.json (different
issue) suggests the author dismisses proposal-file nits.

PR-#54

ⓘ Recommendations generated based on similar findings in past PRs

Evidence
The generator reads data/cves.json, while the installed self-hosted SQL function and managed SQL
view use generated CVE rows rather than reading proposed-cves.json. The new entries exist only in
the proposal and are absent from both the catalog and installed SQL; the scraper workflow also
identifies verification, merging, regeneration, and deletion as steps required before merge.

tools/generate_cve_sql.py[40-51]
tools/generate_cve_sql.py[191-205]
pgFirstAid.sql[2217-2225]
.github/workflows/pgdg-cve-scraper.yml[150-163]
proposed-cves.json[1-13]
data/cves.json[1-24]
tools/generate_cve_sql.py[30-46]
pgFirstAid.sql[2220-2238]
Skill: using-pgfirstaid

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The proposed CVEs are not in the catalog or generated SQL used by installed health checks, so merging this PR alone does not add coverage.

## Fix Focus Areas
- proposed-cves.json[1-13]
- data/cves.json[1-24]
- tools/generate_cve_sql.py[34-46]
- tools/generate_cve_sql.py[191-205]

## Recommended Fix
After human verification, merge the approved entries into `data/cves.json`, regenerate and commit all three SQL files using `tools/generate_cve_sql.py`, and remove `proposed-cves.json` before merging.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Dismiss ↗ | View ↗


Grey Divider

Context sources
✅ Compliance rules (platform): 1 rule
✅ Web pages:
  +1 more
✅ Skills: using-pgfirstaid
Review mode: Auto: ⚖️ Balanced: Security-sensitive catalog with many entries, but repetitive single-file changes.

Grey Divider

Comment thread proposed-cves.json
Comment on lines +3 to +6
"cve_id": "CVE-2026-116304",
"cvss": 8.8,
"summary": "PostgreSQL parallel RECORD typmod use-after-free executes arbitrary code",
"doc_link": "https://www.postgresql.org/support/security/CVE-2026-116304/",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Action required

1. New database flaws go undetected 🐞 Bug ≡ Correctness

proposed-cves.json contains CVE-2026-116304 and other new entries, but neither the curated CVE
catalog nor the generated SQL incorporates them. If this PR merges as submitted, health checks using
the self-hosted function or managed view will not report those vulnerabilities.
Agent Prompt
## Issue description
The proposed CVEs are not in the catalog or generated SQL used by installed health checks, so merging this PR alone does not add coverage.

## Fix Focus Areas
- proposed-cves.json[1-13]
- data/cves.json[1-24]
- tools/generate_cve_sql.py[34-46]
- tools/generate_cve_sql.py[191-205]

## Recommended Fix
After human verification, merge the approved entries into `data/cves.json`, regenerate and commit all three SQL files using `tools/generate_cve_sql.py`, and remove `proposed-cves.json` before merging.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Dismiss ↗ | View ↗

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants