authlib vuln-db entry contains invalid specifier "=1.7.0"

[michael-cybrid]

Safety version

3.8.1

Python version

3.14

Bug description

Running safety check against an environment that contains authlib fails with:

Unhandled exception happened: Invalid specifier: '=1.7.0'

The vulnerability DB entry for authlib contains the specifier =1.7.0 (single equals), which packaging.specifiers.SpecifierSet rejects as invalid per PEP 440 (should be ==1.7.0).

This is the same root cause as #873 (tensorflow). PR #879 fixes the crash in the scan code path but the equivalent call in safety/safety.py:756 (used by the check command) is unpatched.

Fix needed

1. Correct the authlib entry in the vulnerability database: =1.7.0 → ==1.7.0
2. Apply the same try/except InvalidSpecifier guard to safety/safety.py:756 as PR fix: gracefully handle invalid specifiers in vulnerability DB (#873) #879 does for scan/ecosystems/python/main.py:341

Steps to reproduce

Run safety check in an environment with authlib installed.

References

• tensorflow vuln-db entry contains invalid specifier "=2.7.0" #873 (same issue, tensorflow)
• fix: gracefully handle invalid specifiers in vulnerability DB (#873) #879 (partial fix, scan path only)

[github-actions]

Hi @michael-cybrid, thank you for opening this issue!

We appreciate your effort in reporting this. Our team will review it and get back to you soon.
If you have any additional details or updates, feel free to add them to this issue.

Note: If this is a serious security issue that could impact the security of Safety CLI users, please email security@safetycli.com immediately.

Thank you for contributing to Safety CLI!