Skip to main content
No exploitation reported

CVE-2019-16263

No exploitation reported by the sources we read.

  • Published2019-10-07
  • WeaknessCWE-295

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

The Twitter Kit framework through 3.4.2 for iOS does not properly validate the api.twitter.com SSL certificate. Although the certificate chain must contain one of a set of pinned certificates, there are certain implementation errors such as a lack of hostname verification. NOTE: this is an end-of-life product.

Timeline

dates in UTC
  1. 2019-10-0712:15CVE publishedNVD

Versions per branch

NVD
Twitter twitter kit
BranchAffectedFixed in
3.4≤ 3.4.2no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

No fix published by the sources we read yet. NVD record

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Published
2019-10-07
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-9495-4rpc-2jcg

Frequently asked questions

What is CVE-2019-16263?

The Twitter Kit framework through 3.4.2 for iOS does not properly validate the api.twitter.com SSL certificate. Although the certificate chain must contain one of a set of pinned certificates, there are certain implementation errors such as a lack of hostname verification. NOTE: this is an end-of-life product.

Is CVE-2019-16263 actively exploited?

Active exploitation of CVE-2019-16263 has not been confirmed. Its EPSS score was 1.0% on 2026-11-18, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2019-16263?

CVE-2019-16263 has a CVSS v3 base score of 7.4 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record