Who was Korah's father?

What follows is one scholar’s way of reading this disagreement — a critical-historical view that often concludes the texts genuinely disagree. It draws on the peer-reviewed sources listed below and stands as one position among the answers above, presented for transparency, not as GEBible’s position.

How critical scholarship weighs this: Leans toward a genuine contradiction

This summarizes where critical scholarship tends to land on this tension — a report on the field’s center of gravity, not GEBible’s own ruling.

Genesis 36 makes Korah a son of Esau three times and a grandson of Esau once. In the marriage-and-children notices, Korah is a direct son of Esau by his wife Oholibamah: "Oholibamah bare Jeush, Jalam, and Korah" (36:5), repeated at 36:14, and again in the chief-list at 36:18, "the sons of Oholibamah Esau's wife: chief Jeush, chief Jalam, chief Korah." But in the chief-list of Eliphaz's line, Korah appears among the descendants of Eliphaz, Esau's firstborn: "the sons of Eliphaz: chief Teman, chief Omar, chief Zepho, chief Kenaz, chief Korah, chief Gatam, chief Amalek" (36:15-16). On this listing Korah is Esau's grandson through Eliphaz, not his son.

The apologetic standard, run by Archer and reproduced in numerous evangelical study Bibles, posits two different Korahs — one a son of Esau, one a son of Eliphaz — both legitimately recorded. This is not impossible in a genealogy where clan names recur. But the decisive evidence is internal to the chapter, and it does not depend on any disputed manuscript reading. The phrase "chief Korah" in Genesis 36:16 is intrusive: it disrupts the otherwise tidy correspondence between the sons of Eliphaz actually enumerated in 36:11 — Teman, Omar, Zepho, Gatam, and Kenaz — together with Amalek, added in 36:12 as the son of Eliphaz's concubine Timna. Korah is simply not among the sons of Eliphaz listed in 36:11-12; he surfaces only in the parallel chief-list of 36:15-16. A genealogy that names Eliphaz's offspring as five sons plus Amalek, and then a verse or two later lists "chiefs" of Eliphaz that include an additional Korah found nowhere in the offspring list, is internally inconsistent on its own terms. The most economical explanation is that "chief Korah" in 36:16 is a secondary intrusion — a copyist or compiler, aware of the prominent Oholibamah-Korah from 36:5, 14, 18, harmonized or assimilated the chief-list to it, producing a Korah in the Eliphaz line who has no place among Eliphaz's enumerated sons. This is the classic profile of a gloss: a name consistent with one tradition imported into a context where the surrounding data do not support it. (Whether any extant version actually omits the second Korah at 36:16 would need confirmation against the BHS and Wevers apparatus; the internal evidence alone carries the argument, and earlier claims of a clean Samaritan/Greek omission should not be relied on without that verification.)

Richard Friedman's source analysis locates the Esau *tôlĕdōt* in the Priestly layer, which incorporated Edomite king-list and clan material from several hands; the duplications and intrusions throughout Genesis 36 (compare the Anah and Dishon tangles in the same chapter) are characteristic of multiple genealogical sources spliced without full reconciliation. Westermann likewise reads the chapter as composite, distinguishing the king-list, the chief-lists, and the marriage notices as originally separate units. The "two Korahs" defense must assume that the genealogist deliberately gave the same name to a son and a grandson of Esau within the span of a dozen verses, without a word of clarification, and must explain why the supposed Eliphaz-Korah is absent from the very list of Eliphaz's sons that precedes the chief-list. The text-critical and source-critical reading is more economical: the second occurrence is a secondary insertion into a composite, imperfectly harmonized genealogy. Tov's general work on glosses and harmonizing additions describes exactly this category of scribal activity, even where the specific case of 36:16 awaits independent confirmation in the apparatus.

Where the critical reading lands: most plausibly a secondary insertion within a composite Edomite genealogy, not an original double-Korah; a genuine internal inconsistency with the chapter's own structure betraying its secondary origin.