---
title: "@octokit/request-error security advisories"
description: "1 known security advisory for @octokit/request-error, with the versions they affect and the version that fixes each."
url: https://inlinr.com/packages/@octokit/request-error/security
lang: en
---

[Packages](https://inlinr.com/packages)

# @octokit/request-error

7.1.2 · 30 Aug 2026 MIT 56.2M / week [Repository](https://github.com/octokit/request-error.js) [Homepage](https://github.com/octokit/request-error.js#readme) [npm](https://www.npmjs.com/package/@octokit/request-error) [Atom feed](https://inlinr.com/packages/feed/@octokit/request-error)

Your version 

## Security advisories

From OSV, open ones first. Each release line gets its own fix: an older major is fixed by a patch on that major, not by moving to the newest one.

| Line | Newest | Where it stands                                                               |
| ---- | ------ | ----------------------------------------------------------------------------- |
|      | 7.1.2  | No known advisory                                                             |
|      | 6.1.8  | 4 open advisories, worst moderate  · last release Apr 2025, no longer updated |

- Moderate  
[@octokit/request-error has a Regular Expression in index that Leads to ReDoS Vulnerability Due to Catastrophic Backtracking](https://inlinr.com/advisories/GHSA-xx4v-prfh-6cgc)GHSA-xx4v-prfh-6cgc · 14 Feb 2025  
fixed in 6.1.7, 5.1.1

### Quality and security signals

What [npm](https://www.npmjs.com/package/@octokit/request-error) and [deps.dev](https://deps.dev/npm/%40octokit%2Frequest-error) say about the latest release. Signals, not a verdict.

Reading npm and deps.dev…

Reading releases, release notes and advisories…

Registry facts last checked 19 Nov 2026\. Releases and advisories last read 19 Nov 2026.

A whole project to check? Paste its package.json in the [dependency check](https://inlinr.com/tools/dependency-check): every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.
