# Nim version 2.2.14 released

DevFeed: [Nim version 2.2.14 released](<https://devfeed.tech/articles/nim-version-2-2-14-released-105422.md>)

Original publisher: [Read original article](<https://nim-lang.org//blog/2026/10/28/nim-2214.html>)

Published: 2026-10-28T00:00:00Z

Content type: release

Language: en

Sources: [Nim Programming Language](<https://devfeed.tech/sources/nim-programming-language.md>)

Topics: [Nim](<https://devfeed.tech/topics/nim.md>), [releases](<https://devfeed.tech/topics/releases.md>), [TLS (Transport Layer Security)](<https://devfeed.tech/topics/tls.md>), [certificates](<https://devfeed.tech/topics/certificates.md>)

Tags: [1-6](<https://devfeed.tech/tags/1-6.md>), [2-2](<https://devfeed.tech/tags/2-2.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [bugfixes](<https://devfeed.tech/tags/bugfixes.md>), [commits](<https://devfeed.tech/tags/commits.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [headers](<https://devfeed.tech/tags/headers.md>), [improvements](<https://devfeed.tech/tags/improvements.md>), [modules](<https://devfeed.tech/tags/modules.md>), [nim](<https://devfeed.tech/tags/nim.md>), [patch](<https://devfeed.tech/tags/patch.md>), [proxy](<https://devfeed.tech/tags/proxy.md>), [redirect](<https://devfeed.tech/tags/redirect.md>), [release](<https://devfeed.tech/tags/release.md>), [reverse-proxy](<https://devfeed.tech/tags/reverse-proxy.md>), [security](<https://devfeed.tech/tags/security.md>), [security-fixes](<https://devfeed.tech/tags/security-fixes.md>), [stable](<https://devfeed.tech/tags/stable.md>), [standard-library](<https://devfeed.tech/tags/standard-library.md>), [version](<https://devfeed.tech/tags/version.md>)

## AI overview

Nim 2.2.14 is the seventh patch release in the stable 2.2 series, with 142 commits. Its security fixes address credential leakage on cross-origin redirects, HTTP request smuggling and ambiguous body framing, TLS certificate checks for IP addresses and hostnames, request/header injection, parser resource exhaustion, and several other input-handling issues. The excerpt also lists fixes across the compiler, runtime, standard library, tooling, and platform support. Users can install through their OS package manager, update an existing installation with `choosenim update self` and `choosenim update stable` (the release recommends choosenim v0.8.16), or download a nightly build. The supplied text is an excerpt and does not include the complete change list.

## Source excerpt

The Nim Team is happy to announce version 2.2.14, the seventh patch release for our stable release, Nim 2.2. It comes seven weeks after the 2.2.12 release and it contains 142 commits, bringing bugfixes and improvements. If you're still on Nim 1.6, take a look at the version 2.0 release article to see all the features you're missing. If you've been using Nim 2.0, the version 2.2 release article shows the improvements available in Nim 2.2. Installing Nim 2.2.14 Check out if the package manager of your OS already ships version 2.2.14 or install it as described here. If you have installed a previous version of Nim using choosenim, getting Nim 2.2.14 is as easy as: $ choosenim update self $ choosenim update stable NOTE: We recommend that you install and use the latest version of choosenim, v0.8.16, available in our choosenim repo. Alternatively, you can download Nim 2.2.14 from our nightlies builds. Security fixes This release hardens several standard library modules against malicious input: httpclient: on a redirect that leaves the origin (scheme, host, port) of the requested URL, the Authorization, Cookie and Host headers are now dropped, so a server can no longer redirect the client to a host it controls and read its credentials. (STD-001) asynchttpserver: request bodies are now always read completely. Chunked bodies of methods other than POST, chunk extensions and trailer fields could previously be parsed as the next request on the connection, which allowed request smuggling behind a reverse proxy. (STD-002) asynchttpserver: requests with ambiguous body framing (both Content-Length and Transfer-Encoding, repeated or malformed Content-Length, unknown transfer codings, whitespace before the colon) are now rejected following RFC 9112, section 6.3. (STD-003) net, asyncnet: when a TLS client connects to an IP address, the address is now checked against the certificate's IP SANs. Previously any certificate signed by a trusted CA was accepted. (STD-004) cmdline: parseCmdLin