vciy

CVE-2016-8750

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

Apache Karaf prior to 4.0.8 used the LDAPLoginModule to authenticate users to a directory via LDAP

CVE-2016-87504 of 4 sources documented this
19

rank 19 = 1 + 16 + 0 + 2 + 0

rank@v1 · backlog

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.05179  ·  without this subject the record ranks 18

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 6.5, from NVD  ·  without this subject the record ranks 3

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 19

How much of the world it touches

NVD CPE configurations

1 product in the CPE ranges  ·  without this subject the record ranks 17

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 19

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$158,000over the next 30 days, if this record is yours
Movementno material movementthe record holds only daily drift and scoring model releases
Basisassumeda published average, not your estate

$158,000 = $4.99M incident cost x 0.6121449559255632 exposure x 0.05179 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Hindsight · the state

0.05179EPSSNOT IN KEVas of 2026-09-20
Severity6.5 MEDIUMreceipt
Harmpartial impactreceipt
Exploitationnone in held sources
Defenseunaffected versions publishedreceipt
Movementrisenreceipt
PLATEAU10Minimal movement since 2022-02-04, 1675 days at 0.05, as of 2026-09-06. arc-rules@v1

Foresight · where to check next

No weakness class or product neighbourhood is held for this record, so this index cannot name anywhere to check next. That is an absence in the record, not a finding about the software.

Color is a claim, not decoration:the hostile worldthe defenseno signal

Running Apache Karaf? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachnetwork-reachable · low privileges required · no user interaction · low attack complexityreceipt
ImpactComplete availability lossreceipt
Scored fromCVSS v3.0 · NVD's vectorreceipt
Weakness classCWE-90 Improper Neutralization of Special Elements used in an LDAP Query ('LDAP Injection')receipt
Published consequencesCWE-90: Confidentiality, Integrity, Availability: Execute Unauthorized Code or Commands, Read Application Data, Modify Application Data[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

First unaffected version, by branchkaraf 4.0.8receipt
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.

Exploit Status & Known PoCs a ladder, not a score

Current rung: Nothing observed in held sources.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, NVD6.5 MEDIUMreceipt
Exploit probability0.05179 · top 8% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned byapachereceipt
Recorded changes16 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productApache Software Foundation Apache Karafreceipt
Published rangesapache karaf < 4.0.8receipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

Apache Karaf prior to 4.0.8 used the LDAPLoginModule to authenticate users to a directory via LDAP. However, it did not encoding usernames properly and hence was vulnerable to LDAP injection attacks leading to a denial of service. receipt

NVD's analysis a second authority

severity
6.5 CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
weakness
CWE-90
affected versions
apache karaf < 4.0.8

check it yourself access.redhat.com karaf.apache.org securityfocus.com receipt

Movement the material steps

4 Feb 20220.0089
7 Mar 20230.00244 · scoring model v2023.03.01
17 Mar 20250.03388 · scoring model v2025.03.14
15 Jun 20260.0547 · scoring model v2026.06.15
6 Sep 20260.05179
Show all 16 observations
4 Feb 20220.0089
7 Mar 20230.00244
13 Jul 20230.00200
17 Dec 20240.00191
17 Mar 20250.03388
24 Mar 20250.01793
29 Mar 20250.03388
30 Mar 20250.01793
19 May 20250.0151
15 Jun 20260.0547
28 Jun 20260.05277
31 Jul 20260.05179
23 Aug 20260.04391
30 Aug 20260.05179
5 Sep 20260.04391
6 Sep 20260.05179

16 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.05179Published2018-02-19Index as of2026-09-06

The record had been public for 8 years, 6 months when this index was last written.

Published 2018-02-19 receipt · Index as of 2026-09-06 derived

Siblings and hubs

Records related to this one

Browse the index from here

These are index-wide views, not findings about CVE-2016-8750.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.