VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

aws-sdk-s3: vulnerability history, versions and safety

aws-sdk-s3 is a package in the RubyGems ecosystem. Vulert records 1 vulnerability for it across 82 releases, first recorded in Dec 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 18 Dec 2025.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all aws-sdk-s3 vulnerabilities

Vulert verdict on aws-sdk-s3 1.235.0 i

Updated on 23 Oct 2026

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

Package health score 87/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 1.235.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 1 in the last year i
  • Latest disclosure 18 Dec 2025 i
  • Highest CVSS 5.3 i
  • With no published fix 0 i
  • Stars 3,657 i
  • OpenSSF scorecard 6/10 i
  • Last release this month i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by RubyGems, refreshed 23 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 aws-sdk-s3, 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
1.235.0 20 Oct 2026 none Apache-2.0 — Details →
1.234.0 19 Oct 2026 none Apache-2.0 — Details →
1.233.2 06 Oct 2026 none Apache-2.0 — Details →
1.233.1 01 Oct 2026 none Apache-2.0 — Details →
1.233.0 30 Sep 2026 none Apache-2.0 — Details →
1.232.3 28 Sep 2026 none Apache-2.0 — Details →
1.232.2 25 Sep 2026 none Apache-2.0 — Details →
1.232.1 16 Sep 2026 none Apache-2.0 — Details →
1.232.0 11 Sep 2026 none Apache-2.0 — Details →
1.231.0 09 Sep 2026 none Apache-2.0 — Details →
1.230.0 08 Sep 2026 none Apache-2.0 — Details →
1.229.0 06 Aug 2026 none Apache-2.0 — Details →
1.228.2 30 Jul 2026 none Apache-2.0 — Details →
1.228.1 23 Jul 2026 none Apache-2.0 — Details →
1.228.0 16 Jul 2026 none Apache-2.0 — Details →
1.227.0 09 Jul 2026 none Apache-2.0 — Details →
1.226.0 16 Jun 2026 none Apache-2.0 — Details →
1.225.1 10 Jun 2026 none Apache-2.0 — Details →
1.225.0 02 Jun 2026 none Apache-2.0 — Details →
1.224.0 21 May 2026 none Apache-2.0 — Details →
1.223.0 19 May 2026 none Apache-2.0 — Details →
1.222.0 13 May 2026 none Apache-2.0 — Details →
1.221.0 06 May 2026 none Apache-2.0 — Details →
1.220.0 22 Apr 2026 none Apache-2.0 — Details →
1.219.0 07 Apr 2026 none Apache-2.0 — Details →
1.218.0 31 Mar 2026 none Apache-2.0 — Details →
1.217.1 30 Mar 2026 none Apache-2.0 — Details →
1.217.0 18 Mar 2026 none Apache-2.0 — Details →
1.216.0 12 Mar 2026 none Apache-2.0 — Details →
1.215.0 05 Mar 2026 none Apache-2.0 — Details →
1.214.0 04 Mar 2026 none Apache-2.0 — Details →
1.213.0 28 Jan 2026 none Apache-2.0 — Details →
1.212.0 16 Jan 2026 none Apache-2.0 — Details →
1.211.0 08 Jan 2026 none Apache-2.0 — Details →
1.210.1 06 Jan 2026 none Apache-2.0 — Details →
1.210.0 05 Jan 2026 none Apache-2.0 — Details →
1.209.0 23 Dec 2025 none Apache-2.0 — Details →
1.208.0 16 Dec 2025 none Apache-2.0 — Details →
1.207.0 15 Dec 2025 M1 Apache-2.0 Yes Details →
1.206.0 02 Dec 2025 M1 Apache-2.0 Yes Details →
1.205.0 20 Nov 2025 M1 Apache-2.0 Yes Details →
1.204.0 19 Nov 2025 M1 Apache-2.0 Yes Details →
1.203.1 10 Nov 2025 M1 Apache-2.0 Yes Details →
1.203.0 05 Nov 2025 M1 Apache-2.0 Yes Details →
1.202.0 28 Oct 2025 M1 Apache-2.0 Yes Details →
1.201.0 21 Oct 2025 M1 Apache-2.0 Yes Details →
1.200.0 15 Oct 2025 M1 Apache-2.0 Yes Details →
1.199.1 25 Sep 2025 M1 Apache-2.0 Yes Details →
1.199.0 08 Sep 2025 M1 Apache-2.0 Yes Details →
1.198.0 26 Aug 2025 M1 Apache-2.0 Yes Details →
1.197.0 19 Aug 2025 M1 Apache-2.0 Yes Details →
1.196.1 05 Aug 2025 M1 Apache-2.0 Yes Details →
1.196.0 04 Aug 2025 M1 Apache-2.0 Yes Details →
1.195.0 31 Jul 2025 M1 Apache-2.0 Yes Details →
1.194.0 21 Jul 2025 M1 Apache-2.0 Yes Details →
1.193.0 15 Jul 2025 M1 Apache-2.0 Yes Details →
1.192.0 02 Jul 2025 M1 Apache-2.0 Yes Details →
1.191.0 25 Jun 2025 M1 Apache-2.0 Yes Details →
1.190.0 18 Jun 2025 M1 Apache-2.0 Yes Details →
1.189.1 10 Jun 2025 M1 Apache-2.0 Yes Details →
1.189.0 02 Jun 2025 M1 Apache-2.0 Yes Details →
1.188.0 29 May 2025 M1 Apache-2.0 Yes Details →
1.187.0 28 May 2025 M1 Apache-2.0 Yes Details →
1.186.1 15 May 2025 M1 Apache-2.0 Yes Details →
1.186.0 12 May 2025 M1 Apache-2.0 Yes Details →
1.185.0 01 May 2025 M1 Apache-2.0 Yes Details →
1.184.0 28 Apr 2025 M1 Apache-2.0 Yes Details →
1.183.0 31 Mar 2025 M1 Apache-2.0 Yes Details →
1.182.0 18 Feb 2025 M1 Apache-2.0 Yes Details →
1.181.0 14 Feb 2025 M1 Apache-2.0 Yes Details →
1.180.0 06 Feb 2025 M1 Apache-2.0 Yes Details →
1.179.0 29 Jan 2025 M1 Apache-2.0 Yes Details →
1.178.0 15 Jan 2025 M1 Apache-2.0 Yes Details →
1.177.0 03 Jan 2025 M1 Apache-2.0 Yes Details →
1.176.1 12 Dec 2024 M1 Apache-2.0 Yes Details →
1.176.0 03 Dec 2024 M1 Apache-2.0 Yes Details →
1.175.0 02 Dec 2024 M1 Apache-2.0 Yes Details →
1.174.0 25 Nov 2024 M1 Apache-2.0 Yes Details →
1.173.0 21 Nov 2024 M1 Apache-2.0 Yes Details →
1.172.0 18 Nov 2024 M1 Apache-2.0 Yes Details →
1.171.0 14 Nov 2024 M1 Apache-2.0 Yes Details →
1.170.1 11 Nov 2024 M1 Apache-2.0 Yes Details →
1.170.0 06 Nov 2024 M1 Apache-2.0 Yes Details →
1.169.0 18 Oct 2024 M1 Apache-2.0 Yes Details →
1.168.0 16 Oct 2024 M1 Apache-2.0 Yes Details →
1.167.0 02 Oct 2024 M1 Apache-2.0 Yes Details →
1.166.0 24 Sep 2024 M1 Apache-2.0 Yes Details →
1.165.0 23 Sep 2024 M1 Apache-2.0 Yes Details →
1.164.0 20 Sep 2024 M1 Apache-2.0 Yes Details →
1.163.0 18 Sep 2024 M1 Apache-2.0 Yes Details →
1.162.0 11 Sep 2024 M1 Apache-2.0 Yes Details →
1.161.0 10 Sep 2024 M1 Apache-2.0 Yes Details →
1.160.0 03 Sep 2024 M1 Apache-2.0 Yes Details →
1.159.0 20 Aug 2024 M1 Apache-2.0 Yes Details →
1.158.0 15 Aug 2024 M1 Apache-2.0 Yes Details →
1.157.0 01 Aug 2024 M1 Apache-2.0 Yes Details →
1.156.0 02 Jul 2024 M1 Apache-2.0 Yes Details →
1.155.0 28 Jun 2024 M1 Apache-2.0 Yes Details →
1.154.0 25 Jun 2024 M1 Apache-2.0 Yes Details →
1.153.0 24 Jun 2024 M1 Apache-2.0 Yes Details →
1.152.3 13 Jun 2024 M1 — Yes Details →
1.152.2 12 Jun 2024 M1 — Yes Details →
1.152.1 10 Jun 2024 M1 — Yes Details →
1.152.0 05 Jun 2024 M1 — Yes Details →
1.151.0 14 May 2024 M1 — Yes Details →
1.150.0 13 May 2024 M1 — Yes Details →
1.149.1 06 May 2024 M1 — Yes Details →
1.149.0 30 Apr 2024 M1 — Yes Details →
1.148.0 25 Apr 2024 M1 — Yes Details →
1.147.0 16 Apr 2024 M1 — Yes Details →
1.146.1 28 Mar 2024 M1 — Yes Details →
1.146.0 18 Mar 2024 M1 — Yes Details →
1.145.0 15 Mar 2024 M1 — Yes Details →
1.144.0 13 Mar 2024 M1 — Yes Details →
1.143.1 12 Mar 2024 M1 — Yes Details →
1.143.0 26 Jan 2024 M1 — Yes Details →
1.142.0 22 Dec 2023 M1 — Yes Details →
1.141.0 28 Nov 2023 M1 — Yes Details →
1.140.0 27 Nov 2023 M1 — Yes Details →
1.139.0 22 Nov 2023 M1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 1

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

03 Vulnerabilities

Recorded vulnerabilities for aws-sdk-s3

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-14762: AWS SDK for Ruby S3 Encryption Client Key Commitment Issue 5.3 medium 1.208.0 18 Dec 2025

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 aws-sdk-s3

Is aws-sdk-s3 safe to use?

Vulert records 1 vulnerabilities for aws-sdk-s3 in RubyGems: 0 critical, 0 high, 1 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 aws-sdk-s3's Vulert package health score?

Vulert scores aws-sdk-s3 87/100, which reads as healthy. 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 aws-sdk-s3 affected?

No. 1.235.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.

How many vulnerabilities does aws-sdk-s3 have?

1 vulnerability is recorded for aws-sdk-s3 in the RubyGems ecosystem: 0 critical, 0 high, 1 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 aws-sdk-s3 vulnerabilities disclosed?

1 vulnerability was recorded for aws-sdk-s3 in the last 12 months, and the oldest entry in this database dates to 18 Dec 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 aws-sdk-s3 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 aws-sdk-s3 for upcoming vulnerabilities?

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