How severe is CVE-2016-1899?

CVE-2016-1899 has a CVSS 3.x base score of 3.7, rated low severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity low, and availability none.

Is CVE-2016-1899 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (78th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2016-1899?

CVE-2016-1899 primarily affects Cgit Project Cgit. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2016-1899?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2016-1899 published?

CVE-2016-1899 was published on 2016-01-20 and last updated on 2026-06-17.

CVE-2016-1899

CVE-2016-1899 is a low-severity vulnerability in Cgit Project Cgit with a CVSS 3.x base score of 3.7. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Low (CVSS 3.x base score 3.7)
CVSS v2: 4.3
EPSS exploit prediction: 2% (78th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Cgit Project Cgit
Published: 2016-01-20
Last modified: 2026-06-17

Description

CRLF injection vulnerability in the ui-blob handler in CGit before 0.12 allows remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks or cross-site scripting (XSS) attacks via CRLF sequences in the mimetype parameter, as demonstrated by a request to blob/cgit.c.

Frequently asked questions

What is CVE-2016-1899?: CRLF injection vulnerability in the ui-blob handler in CGit before 0.12 allows remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks or cross-site scripting (XSS) attacks via CRLF sequences in the mimetype parameter, as demonstrated by a request to blob/cgit.c.
How severe is CVE-2016-1899?: CVE-2016-1899 has a CVSS 3.x base score of 3.7, rated low severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity low, and availability none.
Is CVE-2016-1899 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (78th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2016-1899?: CVE-2016-1899 primarily affects Cgit Project Cgit. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2016-1899?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2016-1899 published?: CVE-2016-1899 was published on 2016-01-20 and last updated on 2026-06-17.

References

Affected products (2)

cpe:2.3:o:fedoraproject:fedora:22:*:*:*:*:*:*:*
cpe:2.3:a:cgit_project:cgit:*:*:*:*:*:*:*:*

More vulnerabilities in Cgit Project Cgit

CVE-2016-1901 — Critical (CVSS 9.8): Integer overflow in the authenticate_post function in CGit before 0.12 allows remote attackers to have unspecified…
CVE-2018-14912 — High (CVSS 7.5): cgit_clone_objects in CGit before 1.2.1 has a directory traversal vulnerability when `enable-http-clone=1` is not…
CVE-2016-1900 — Low (CVSS 3.7): CRLF injection vulnerability in the cgit_print_http_headers function in ui-shared.c in CGit before 0.12 allows remote…

All CVEs affecting Cgit Project Cgit →