Dev.to Security πŸ” Cybersecurity πŸ‘ 0 πŸ“– 2 min read

Dependabot knows why it can't fix your alert. It just doesn't tell you.

Last week I measured how many popular Python projects have security alerts that no upgrade can close, because every fixed release needs a newer Python. About half of the projects with alerts had at least one. I wanted t

Last week I measured how many popular Python projects have security alerts that no upgrade can close, because every fixed release needs a newer Python. About half of the projects with alerts had at least one.

I wanted to see what Dependabot says in that case. So I made a tiny public repo and let Dependabot run on it.

The setup

  • requires-python = ">=3.10"
  • beautifulsoup4 and pillow as dependencies
  • In uv.lock: soupsieve 2.8.3 (it comes with beautifulsoup4) and pillow 12.2.0

Every fixed soupsieve release from 3.0.2 up needs Python 3.11.5. The fixed pillow 13 needs Python 3.11. This project still allows 3.10.

Repo: https://github.com/samuelrojas-dev/depquiet-floor-test

What Dependabot showed for soupsieve

Dependabot cannot update soupsieve to a non-vulnerable version
The latest possible version of soupsieve that can be installed is 2.8.3.
The earliest fixed version is 4.0.

That's all. No reason. The error in the job log has an empty conflicting-dependencies list.

But the same log has this line, once for every release from 3.0.2 to 4.1.3:

Filtered out soupsieve 4.0 because python requirement >= 3.11.5 is not satisfied by python 3.10.22

So Dependabot finds the reason. It just doesn't show it on the alert.

Two more things surprised me:

  • One alert said "Patched version: 2.8.4", and right above it Dependabot said "The earliest fixed version is 4.0".
  • soupsieve 2.10 does install on Python 3.10, and it fixes 5 of the 8 soupsieve alerts. Dependabot said the latest version it could install was 2.8.3.

What Dependabot did for pillow

It opened a pull request: pillow 12.2.0 β†’ 12.3.0. That closes 13 alerts. The other 43 are only fixed in pillow 13, which needs Python 3.11, and the pull request doesn't say that. If you merge it, you'd probably think you were done.

What would actually help

Tell me the real choice:

  1. Raise requires-python to >=3.11.5, and all the fixes install.
  2. Or keep Python 3.10, take the partial fixes now (soupsieve 2.10, pillow 12.3.0), and accept the rest.

I opened an issue on dependabot-core with the repro: https://github.com/dependabot/dependabot-core/issues/16987

What depquiet says on the same repo

I built depquiet for this kind of case, so I ran it on the same repo:

βœ“ pillow 12.2.0 β†’ 12.3.0: the newest fix your Python range allows (closes 13 of 55 alerts; the other 42 need Python >=3.11)
βœ“ soupsieve 2.8.3 β†’ 2.10.0: the newest fix your Python range allows (closes 5 of 8 alerts; the other 3 need Python >=3.11.5)
βœ— pillow β†’ 13.0.0: needs a newer Python: see Python floor below
βœ— soupsieve β†’ 4.0.0: needs a newer Python: see Python floor below

Python floor:
  Raising requires-python to >=3.11.5 would let 2 fixes install (pillow, soupsieve; 63 alerts), verified with uv's resolver.

(depquiet reads advisories through pip-audit, so its pillow count is 55, not GitHub's 56.)

You can try it without installing anything:

uvx --with pip-audit depquiet --fix-plan

Repo: https://github.com/samuelrojas-dev/depquiet

πŸ“° Read the original article on Dev.to Security

Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes β€” full credit and traffic to the original publisher.