How severe is GHSA-r82c-j4mq-5xfw?

No CVSS score has been assigned to GHSA-r82c-j4mq-5xfw yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-r82c-j4mq-5xfw?

GHSA-r82c-j4mq-5xfw affects the following packages: bitlyshortener (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-r82c-j4mq-5xfw?

Update bitlyshortener to 0.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r82c-j4mq-5xfw is resolved across your whole dependency graph.

How do I detect GHSA-r82c-j4mq-5xfw in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for bitlyshortener, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-r82c-j4mq-5xfw if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-r82c-j4mq-5xfw?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-r82c-j4mq-5xfw can be triaged on real exposure rather than presence alone.

Is GHSA-r82c-j4mq-5xfw actively exploited in the wild?

No public exploit code has been indexed for GHSA-r82c-j4mq-5xfw yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-r82c-j4mq-5xfw published, and has it been updated?

GHSA-r82c-j4mq-5xfw was published on October 27, 2020 and was last updated on December 2, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

GHSA-r82c-j4mq-5xfw — bitlyshortener

Fix: impredicative/bitlyshortener@3d412fe

GHSA-r82c-j4mq-5xfw is a security vulnerability in bitlyshortener. A fix is available for bitlyshortener — see the affected versions and patch details below.

Update bitlyshortener to >=0.5.0 to prevent generating some invalid short URLs

Published

Oct 27, 2020

Updated

Dec 2, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Dec 2, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐍bitlyshortener

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Impact

Due to a sudden upstream breaking change by Bitly, versions of bitlyshortener <0.5.0 can generate an invalid short URL when a vanity domain exists.

Patches

Upgrading bitlyshortener to 0.5.0 or newer will prevent the generation of any such invalid short URLs.

References

Release notes

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`bitlyshortener`	all versions	0.5.0`pip install --upgrade 'bitlyshortener==0.5.0'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for bitlyshortener, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update bitlyshortener to 0.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r82c-j4mq-5xfw is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-r82c-j4mq-5xfw can be triaged on real exposure rather than presence alone.

Tailored to GHSA-r82c-j4mq-5xfw. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Due to a sudden upstream breaking change by Bitly, versions of `bitlyshortener` <0.5.0 can generate an invalid short URL when a vanity domain exists. ### Patches Upgrading `bitlyshortener` to 0.5.0 or newer will prevent the generation of any such invalid short URLs. ### References * [Release notes](https://github.com/impredicative/bitlyshortener/releases)

O3 Security · Impact-Aware SCA

Is GHSA-r82c-j4mq-5xfw in your dependencies?

O3 Security finds GHSA-r82c-j4mq-5xfw across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works