VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@sap/approuter: vulnerability history, versions and safety

@sap/approuter is a package in the npm ecosystem. Vulert records 4 vulnerabilities for it across 118 releases, from Feb 2025 to Aug 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded C1 H3
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
3 in the last 12 months

Most recent disclosure 11 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all @sap/approuter vulnerabilities

Vulert verdict on @sap/approuter 23.3.0 i

Updated on 23 Oct 2026

Good news: 23.3.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 4.

Package health score 69/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Not enough data

What to do: Stay on 23.3.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 23.3.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 23.3.0 — unaffected i
  • Vulnerabilities on record 4 over 1 year · 3 in the last year i
  • Latest disclosure 11 Aug 2026 i
  • Highest CVSS 9.1 i
  • With no published fix 0 i
  • Depended on by 3 packages i
  • Last release this month i
  • Licence non-standard i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for @sap/approuter, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
23.3.0 01 Oct 2026 none non-standard — Details →
23.0.0 11 Aug 2026 none non-standard — Details →
22.0.3 18 Jun 2026 H1 non-standard Yes Details →
22.0.2 16 Jun 2026 H1 non-standard Yes Details →
22.0.1 25 May 2026 H1 non-standard Yes Details →
22.0.0 16 May 2026 H1 non-standard Yes Details →
21.5.0 11 May 2026 H1 non-standard Yes Details →
21.4.0 28 Apr 2026 H1 non-standard Yes Details →
21.3.0 14 Apr 2026 H1 non-standard Yes Details →
21.2.1 09 Apr 2026 H1 non-standard Yes Details →
21.2.0 28 Mar 2026 H1 non-standard Yes Details →
21.1.0 16 Mar 2026 H2 non-standard Yes Details →
21.0.0 02 Mar 2026 H2 non-standard Yes Details →
20.10.0 19 Feb 2026 H2 non-standard Yes Details →
20.9.0 09 Feb 2026 C1 H2 non-standard Yes Details →
20.8.8 11 Jan 2026 C1 H2 non-standard Yes Details →
20.8.7 01 Jan 2026 C1 H2 non-standard Yes Details →
20.8.6 15 Dec 2025 C1 H2 non-standard Yes Details →
20.8.5 10 Dec 2025 C1 H2 non-standard Yes Details →
20.8.4 03 Dec 2025 C1 H2 non-standard Yes Details →
20.8.3 12 Nov 2025 C1 H2 non-standard Yes Details →
20.8.2 28 Sep 2025 C1 H2 non-standard Yes Details →
20.8.1 17 Sep 2025 C1 H2 non-standard Yes Details →
20.8.0 16 Sep 2025 C1 H2 non-standard Yes Details →
20.7.1 28 Aug 2025 C1 H2 non-standard Yes Details →
20.7.0 07 Aug 2025 C1 H2 non-standard Yes Details →
20.6.1 18 Jul 2025 C1 H2 non-standard Yes Details →
20.6.0 03 Jul 2025 C1 H2 non-standard Yes Details →
20.5.4 24 Jun 2025 C1 H2 non-standard Yes Details →
20.5.3 15 Jun 2025 C1 H2 non-standard Yes Details →
20.5.2 15 Jun 2025 C1 H2 non-standard Yes Details →
20.5.1 03 Jun 2025 C1 H2 non-standard Yes Details →
20.5.0 29 May 2025 C1 H2 non-standard Yes Details →
20.4.0 14 May 2025 C1 H2 non-standard Yes Details →
20.3.1 28 Apr 2025 C1 H2 non-standard Yes Details →
20.3.0 20 Apr 2025 C1 H2 non-standard Yes Details →
20.2.0 08 Apr 2025 C1 H2 non-standard Yes Details →
20.1.0 03 Apr 2025 C1 H2 non-standard Yes Details →
20.0.1 31 Mar 2025 C1 H2 non-standard Yes Details →
20.0.0 20 Mar 2025 C1 H2 non-standard Yes Details →
19.0.4 12 Mar 2025 C1 H2 non-standard Yes Details →
19.0.3 12 Mar 2025 C1 H2 non-standard Yes Details →
19.0.2 04 Mar 2025 C1 H2 non-standard Yes Details →
19.0.1 27 Feb 2025 C1 H2 non-standard Yes Details →
19.0.0 30 Jan 2025 C1 H2 non-standard Yes Details →
18.0.3 23 Jan 2025 C1 H2 non-standard Yes Details →
18.0.2 20 Jan 2025 C1 H2 non-standard Yes Details →
18.0.1 09 Jan 2025 C1 H2 non-standard Yes Details →
18.0.0 09 Dec 2024 C1 H2 non-standard Yes Details →
17.1.0 12 Nov 2024 C1 H2 non-standard Yes Details →
17.0.0 28 Oct 2024 C1 H2 non-standard Yes Details →
16.9.0 10 Oct 2024 C1 H2 non-standard Yes Details →
16.8.2 29 Sep 2024 C1 H2 non-standard Yes Details →
16.8.1 24 Sep 2024 C1 H2 non-standard Yes Details →
16.8.0 16 Sep 2024 C1 H2 non-standard Yes Details →
16.7.3 05 Sep 2024 C1 H2 non-standard Yes Details →
16.7.2 04 Sep 2024 C1 H2 non-standard Yes Details →
16.7.1 23 Aug 2024 C1 H3 non-standard Yes Details →
16.7.0 15 Aug 2024 C1 H3 non-standard Yes Details →
16.6.2 31 Jul 2024 C1 H3 non-standard Yes Details →
16.6.1 22 Jul 2024 C1 H3 non-standard Yes Details →
16.6.0 25 Jun 2024 C1 H3 non-standard Yes Details →
16.5.2 09 Jun 2024 C1 H3 non-standard Yes Details →
16.5.1 02 Jun 2024 C1 H3 non-standard Yes Details →
16.5.0 19 May 2024 C1 H3 non-standard Yes Details →
16.4.2 02 May 2024 C1 H3 non-standard Yes Details →
16.4.1 16 Apr 2024 C1 H3 non-standard Yes Details →
16.4.0 14 Apr 2024 C1 H3 non-standard Yes Details →
16.3.0 02 Apr 2024 C1 H3 non-standard Yes Details →
16.2.1 13 Mar 2024 C1 H3 non-standard Yes Details →
16.2.0 05 Mar 2024 C1 H3 non-standard Yes Details →
16.1.1 19 Feb 2024 C1 H3 non-standard Yes Details →
16.1.0 04 Feb 2024 C1 H3 non-standard Yes Details →
16.0.2 10 Jan 2024 C1 H3 non-standard Yes Details →
16.0.1 04 Jan 2024 C1 H3 non-standard Yes Details →
16.0.0 31 Dec 2023 C1 H3 non-standard Yes Details →
15.0.0 18 Dec 2023 C1 H3 non-standard Yes Details →
14.4.3 07 Dec 2023 C1 H3 non-standard Yes Details →
14.4.2 30 Nov 2023 C1 H3 non-standard Yes Details →
14.4.1 27 Nov 2023 C1 H3 non-standard Yes Details →
14.4.0 19 Nov 2023 C1 H3 non-standard Yes Details →
14.3.4 25 Oct 2023 C1 H3 non-standard Yes Details →
14.3.3 12 Oct 2023 C1 H3 non-standard Yes Details →
14.3.2 11 Sep 2023 C1 H3 non-standard Yes Details →
14.3.1 05 Sep 2023 C1 H3 non-standard Yes Details →
14.3.0 30 Jul 2023 C1 H3 non-standard Yes Details →
14.2.1 23 Jul 2023 C1 H3 non-standard Yes Details →
14.2.0 11 Jul 2023 C1 H3 non-standard Yes Details →
14.1.2 13 Jun 2023 C1 H3 non-standard Yes Details →
14.1.1 21 Mar 2023 C1 H3 non-standard Yes Details →
14.1.0 21 Mar 2023 C1 H3 non-standard Yes Details →
14.0.0 10 Feb 2023 C1 H3 non-standard Yes Details →
13.1.1 30 Jan 2023 C1 H3 non-standard Yes Details →
13.1.0 24 Jan 2023 C1 H3 non-standard Yes Details →
13.0.2 15 Jan 2023 C1 H3 non-standard Yes Details →
13.0.1 03 Jan 2023 C1 H3 non-standard Yes Details →
13.0.0 25 Dec 2022 C1 H3 non-standard Yes Details →
12.0.3 11 Dec 2022 C1 H3 non-standard Yes Details →
12.0.2 06 Dec 2022 C1 H3 non-standard Yes Details →
12.0.1 30 Nov 2022 C1 H3 non-standard Yes Details →
12.0.0 13 Nov 2022 C1 H3 — Yes Details →
11.6.1 03 Nov 2022 C1 H3 — Yes Details →
11.6.0 24 Oct 2022 C1 H3 — Yes Details →
11.5.1 13 Oct 2022 C1 H3 — Yes Details →
11.5.0 18 Sep 2022 C1 H3 — Yes Details →
11.4.1 11 Sep 2022 C1 H3 — Yes Details →
11.4.0 05 Sep 2022 C1 H3 — Yes Details →
11.3.4 30 Aug 2022 C1 H3 — Yes Details →
11.3.3 25 Aug 2022 C1 H3 — Yes Details →
11.3.2 04 Aug 2022 C1 H3 — Yes Details →
11.3.1 28 Jul 2022 C1 H3 — Yes Details →
11.3.0 20 Jul 2022 C1 H3 — Yes Details →
11.2.1 15 Jun 2022 C1 H3 — Yes Details →
11.2.0 14 Jun 2022 C1 H3 — Yes Details →
11.1.0 06 Jun 2022 C1 H3 — Yes Details →
11.0.1 15 May 2022 C1 H3 — Yes Details →
11.0.0 09 May 2022 C1 H3 — Yes Details →
10.15.4 08 May 2022 C1 H3 — Yes Details →
10.15.3 26 Apr 2022 C1 H3 — Yes Details →
10.15.2 24 Apr 2022 C1 H3 — Yes Details →

The newest 120 of 239 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 1
  • 2026 3

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 3 of the 4 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for @sap/approuter

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-27690: SAP Approuter HTTP Request Smuggling Vulnerability 9.1 critical 20.10.0 14 Jul 2026
CVE-2025-24876: Authentication Bypass in @sap/approuter 8.1 high 16.7.2 11 Feb 2025
CVE-2026-44745: SAP Approuter Open Redirect Vulnerability 8.1 high 21.2.0 14 Jul 2026
CVE-2026-58230: SAP Approuter Information Disclosure Vulnerability 7.0 high 23.0.0 11 Aug 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About @sap/approuter

Is @sap/approuter safe to use?

Vulert records 4 vulnerabilities for @sap/approuter in npm: 1 critical, 3 high, 0 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is @sap/approuter's Vulert package health score?

Vulert scores @sap/approuter 69/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of @sap/approuter affected?

No. 23.3.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of @sap/approuter should I use?

23.3.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does @sap/approuter have?

4 vulnerabilities are recorded for @sap/approuter in the npm ecosystem: 1 critical, 3 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new @sap/approuter vulnerabilities disclosed?

3 vulnerabilities were recorded for @sap/approuter in the last 12 months, and the oldest entry in this database dates to 11 Feb 2025. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of @sap/approuter are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor @sap/approuter for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @sap/approuter version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.