chore: clean up stale Dependabot alerts - #834
Merged
John Kennedy (jkennedyvz) merged 2 commits intoJul 14, 2026
Merged
Conversation
John Kennedy (jkennedyvz)
enabled auto-merge (squash)
July 14, 2026 08:32
Co-authored-by: open-swe[bot] <open-swe@users.noreply.github.com>
Facundo Santiago (santiagxf)
pushed a commit
that referenced
this pull request
Jul 28, 2026
…2026-59935) (#872) pypdf ==6.11.0 is vulnerable to an infinite loop via crafted PDFs with unterminated inline images using ASCII85/ASCIIHex filters. Fixed in 6.14.2. ## Changes - **`samples/react-agent-docintelligence/pyproject.toml`**: Added `[tool.uv] constraint-dependencies` to enforce `pypdf>=6.14.2`. This guards against the vulnerable version being resolved if pypdf enters the transitive graph in the future. - **`samples/cosmosdb-nosql/langchain_rag.ipynb`**: Pinned `pypdf>=6.14.2` in the `%pip install` cell (was unpinned). - **`samples/rag-storage-document-loaders/requirements.txt`**: Already pinned to `pypdf==6.14.2` — no change needed. ## Reachability Assessment **Not currently reachable — high confidence.** The Dependabot alert references `samples/uv.lock`, an orphaned workspace-level lock file removed in PR #834. It no longer exists. Running `uv lock` against `react-agent-docintelligence` confirms pypdf is absent from all 151 resolved packages — none of the direct dependencies (`langchain==1.3.14`, `langchain-azure-ai[opentelemetry,tools]`, `langchain-azure-dynamic-sessions`) pull it in. The `constraint-dependencies` entry is a forward-looking guard, not a fix for an active exposure. <!-- START COPILOT ORIGINAL PROMPT --> <details> <summary>Original prompt</summary> > > ---- > > *This section details the Dependabot vulnerability alert you should resolve* > > <alert_title>pypdf: Possible infinite loop for not terminated inline images (ASCII85 and ASCIIHex filter)</alert_title> > <alert_description>### Impact > > An attacker who uses this vulnerability can craft a PDF which leads to an infinite loop. This requires parsing the content stream of a page with a not terminated inline image, as done when extracting the page text for example. It only affects the ASCII85 and ASCIIHex filters. > > ### Patches > > This has been fixed in [pypdf==6.14.2](https://github.com/py-pdf/pypdf/releases/tag/6.14.2). > > ### Workarounds > > If you cannot upgrade yet, consider applying the changes from PR [#3892](https://github.com/py-pdf/pypdf/pull/3892).</alert_description> > > <severity>high</severity> > <identifiers>GHSA-g867-7843-wf8q, CVE-2026-59935</identifiers> > <package>pypdf</package> > <ecosystem>pip</ecosystem> > <vulnerable_versions>= 6.11.0</vulnerable_versions> > <patched_version>6.14.2</patched_version> > <manifest_path>samples/uv.lock</manifest_path> > > <references> > <url>https://github.com/py-pdf/pypdf/security/advisories/GHSA-g867-7843-wf8q</url> > <url>https://nvd.nist.gov/vuln/detail/CVE-2026-59935</url> > <url>https://github.com/py-pdf/pypdf/pull/3892</url> > <url>https://github.com/py-pdf/pypdf/commit/5a33a46416aa1ae6c025ff90a3cca57631fdafd2</url> > <url>https://github.com/py-pdf/pypdf/releases/tag/6.14.2</url> > <url>https://github.com/advisories/GHSA-g867-7843-wf8q</url> > </references> > > <task_instructions>Resolve this alert by updating the affected package to a non-vulnerable version. Prefer the lowest non-vulnerable version (see the patched_version field above) over the latest to minimize breaking changes. Include a Reachability Assessment section in the PR description. Review the alert_description field to understand which APIs, features, or configurations are affected, then search the codebase for usage of those specific items. If the vulnerable code path is reachable, explain how (which files, APIs, or call sites use the affected functionality) and note that the codebase is actively exposed to this vulnerability. If the vulnerable code path is not reachable, explain why (e.g. the affected API is never called, the vulnerable configuration is not used) and note that the update is primarily to satisfy vulnerability scanners rather than to address an active risk. If the advisory is too vague to determine reachability (e.g. 'improper input validation' with no specific API named), state that reachability could not be determined and explain why. Include a confidence level in the reachability assessment (e.g. high confidence if the advisory names a specific API and you confirmed it is or is not called, low confidence if the usage is indirect and hard to trace). If no patched version is available, check the alert_description field for a Workarounds section — the advisory may describe configuration changes or usage patterns that mitigate the vulnerability without a version update. If a workaround is available, apply it and leave a code comment referencing the advisory identifier explaining it is a temporary mitigation. If neither a patch nor a workaround is available, explain in the PR description why the alert cannot be resolved automatically so a human reviewer can take over. Inspect the repository to determine which package manager is used (e.g. lock files, config files, build scripts) and use that tooling to perform the update — do not edit lock files directly. If the version constraint in the manifest (e.g. package.json, Gemfile, pyproject.toml) caps the version below the fix, update the constraint first. For transitive dependencies, determine whether it is simpler to update the direct dependency that pulls in the vulnerable package or to update the transitive dependency directly, and choose the least disruptive approach. If upgrading to fix the vulnerability forces a major version bump or known breaking changes, review the changelog or release notes, then audit the codebase for usage of affected APIs and fix any breaking changes that are found. If the package manager fails to resolve dependencies (e.g. peer dependency conflicts, incompatible engine constraints), document the error in the PR description rather than attempting increasingly complex workarounds. After updating, check the lock file to confirm the package no longer resolves to a version in the vulnerable range. Keep changes minimal and tightly scoped. Ensure tests, build, type checking, and linting all pass after your changes. If there are any test, lint, or typechecking failures, investigate whether they are caused by the update and fix them if so — do not leave broken tests in the PR. If they were already present before the update, note them in the PR description so a human reviewer can assess whether they are related.</task_instructions> > </details> <!-- START COPILOT CODING AGENT SUFFIX --> - Resolves langchain-ai/langchain-azure alert #736 --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
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
1 participant
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
samples/uv.lockand invalid/samplesuv Dependabot target.gitignorecoverage for common secret filesValidation
UV_PYTHON=3.13 NO_COLOR=1 make -C libs/azure-postgresql lint(source lint passes; tests still report existing missing-docstring violations)NO_COLOR=1 uv run --directory libs/azure-postgresql --python 3.13 --frozen --no-default-groups --all-extras --group test_integration --group test pytest -m compile tests/integration_testsVectorinputs; targeted DB MMR test skipped locally becausePGHOSTis not setMade by Open SWE