NVD / CVE Program· CNA redhat

CVE-2016-0746: Use-after-free vulnerability in the resolver in nginx 0.6.18 through 1.8.0 and 1.9.x before 1.9.10 allows remote attackers to cause a denial…

CriticalCVSS 9.8 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Plan (action score 42/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 8.8% (FIRST EPSS); higher than 95.2% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
Fixed version: nginx (Debian:12) 1.9.10-1; nginx (Debian:7) 1.2.1-2.2+wheezy4; nginx (Debian:8) 1.6.2-5+deb8u1.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Add it to your regular patch cycle. Upgrade to nginx (Debian:12) 1.9.10-1; nginx (Debian:7) 1.2.1-2.2+wheezy4; nginx (Debian:8) 1.6.2-5+deb8u1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Use-after-free vulnerability in the resolver in nginx 0.6.18 through 1.8.0 and 1.9.x before 1.9.10 allows remote attackers to cause a denial of service (worker process crash) or possibly have unspecified other impact via a crafted DNS response related to CNAME response processing.

Published: Feb 15, 2016
Updated: Jun 16, 2026
EPSS: 8.8% · 95th percentile
CWE: CWE-416

Report tools

JSON

Action score

Plan

Add it to your regular patch cycle.

CVSS: 39 / 40 · 9.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 3 / 30 · 8.8%

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Is nginx on your server exposed to the internet?Run a port scan

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
f5	nginx	cpe:2.3:a:f5:nginx
canonical	ubuntu linux	cpe:2.3:o:canonical:ubuntu_linux
debian	debian linux	cpe:2.3:o:debian:debian_linux
opensuse	leap	cpe:2.3:o:opensuse:leap
apple	xcode	cpe:2.3:a:apple:xcode

Using nginx? Add it to your stack and be the first to know about CVEs like this one. (Nginx)

Is nginx on your server exposed to the internet?

The free port scanner finds the open ports on your server and matches the service versions it can read against known vulnerabilities. No account needed.

Run a port scan

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

f5 nginx0.6.18 and later · up to 1.8.0 inclusive
f5 nginx1.9.0 and later · before 1.9.10

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	nginx	before 1.9.10-1	1.9.10-1
Debian:7	nginx	before 1.2.1-2.2+wheezy4	1.2.1-2.2+wheezy4
Debian:8	nginx	before 1.6.2-5+deb8u1	1.6.2-5+deb8u1
openSUSE:Tumbleweed	nginx	before 1.11.4-2.5	1.11.4-2.5
Red Hat:rhel_software_collections:2::el6	rh-nginx18-nginx	before 1:1.8.1-1.el6	1:1.8.1-1.el6
Red Hat:rhel_software_collections:2::el6	rh-nginx18-nginx-debuginfo	before 1:1.8.1-1.el6	1:1.8.1-1.el6
Red Hat:rhel_software_collections:2::el7	rh-nginx18-nginx	before 1:1.8.1-1.el7	1:1.8.1-1.el7
Red Hat:rhel_software_collections:2::el7	rh-nginx18-nginx-debuginfo	before 1:1.8.1-1.el7	1:1.8.1-1.el7
SUSE:Lifecycle Management Server 1.3	GeoIP	before 1.4.7-2.10.1	1.4.7-2.10.1
SUSE:Lifecycle Management Server 1.3	nginx-1.0	before 1.0.15-0.29.2	1.0.15-0.29.2

Same product

f5: all records

Other highest-scoring records for the same primary product.

CVE-2013-2028The ngx_http_parse_chunked function in http/ngx_http_parse.c in nginx 1.3.9 through 1.4.0 allows remote attackers to cause a denial of…
56Plan
CVE-2016-0742The resolver in nginx before 1.8.1 and 1.9.x before 1.9.10 allows remote attackers to cause a denial of service (invalid pointer…
55Plan
CVE-2009-2629Buffer underflow in src/http/ngx_http_parse.c in nginx 0.1.0 through 0.5.37, 0.6.x before 0.6.39, 0.7.x before 0.7.62, and 0.8.x before 0.8.
53Plan

Published before and after this one in the same product

← EarlierCVE-2014-3616Dec 8, 2014 · nginx 0.5.6 through 1.7.4, when using the same shared ssl_session_cache or ssl_session_ticket_key for multiple servers, can reuse a cached…
19Monitor
← EarlierCVE-2014-3556Dec 29, 2014 · The STARTTLS implementation in mail/ngx_mail_smtp_handler.c in the SMTP proxy in nginx 1.5.x and 1.6.x before 1.6.1 and 1.7.x before 1.7.4…
29Monitor
Later →CVE-2016-0747Feb 15, 2016 · The resolver in nginx before 1.8.1 and 1.9.x before 1.9.10 does not properly limit CNAME resolution, which allows remote attackers to cause…
24Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
debian:nginx	1.9.10-1 · Debian:12	Package registry (OSV)
opensuse:nginx	1.11.4-2.5 · openSUSE:Tumbleweed	Package registry (OSV)
red hat:rh-nginx18-nginx	1:1.8.1-1.el6 · Red Hat:rhel_software_collections:2::el6	Package registry (OSV)
red hat:rh-nginx18-nginx-debuginfo	1:1.8.1-1.el6 · Red Hat:rhel_software_collections:2::el6	Package registry (OSV)
suse:GeoIP	1.4.7-2.10.1 · SUSE:Lifecycle Management Server 1.3	Package registry (OSV)
suse:nginx-1.0	1.0.15-0.29.2 · SUSE:Lifecycle Management Server 1.3	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-19-115 · Aug 22, 2019(NGINX Sunucu Güvenlik Güncellemesi)

All national notices →

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log (1)

Fix✗ → ✓Sep 28, 2026, 10:46 PM UTC

For records you follow, these changes also arrive as notifications. →

References

lists.opensuse.org/opensuse-updates/2016-02/msg00042.html

Show all references (10 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records