enum-map

Version	Released
`3.1.0` minor	Jul 21, 2026
`3.0.0` major yanked 1 CVE	Jul 20, 2026
`2.7.3` patch	Nov 24, 2023
`2.7.2` patch yanked	Nov 16, 2023
`3.0.0-beta.2` pre yanked 1 CVE	Nov 08, 2023
`2.7.1` patch	Nov 08, 2023
`3.0.0-beta.1` pre yanked 1 CVE	Oct 23, 2023
`2.7.0` minor	Oct 20, 2023
`3.0.0-0.gat.0` pre yanked 1 CVE	Sep 23, 2023
`2.6.3` patch	Sep 10, 2023
`2.6.2` patch	Sep 07, 2023
`2.6.1` patch	Aug 01, 2023
`2.6.0` minor	Jun 30, 2023
`2.5.0` minor	Mar 14, 2023
`2.4.2` patch	Dec 17, 2022
`2.4.1` patch	Jul 28, 2022
`2.4.0` minor	Jun 15, 2022
`2.3.0` minor	May 29, 2022
`2.2.0` minor	May 20, 2022
`2.1.0` minor	Mar 24, 2022
`2.0.3` patch	Feb 26, 2022
`0.6.6` patch	Feb 18, 2022
`0.6.5` patch	Feb 18, 2022
`2.0.2` patch	Feb 17, 2022
`2.0.1` patch yanked 1 CVE	Jan 27, 2022
`2.0.0` major yanked 1 CVE	Jan 10, 2022
`2.0.0-2` pre yanked 1 CVE	Jan 04, 2022
`2.0.0-1` pre	Oct 01, 2021
`1.1.1` patch	May 16, 2021
`1.1.0` minor	May 04, 2021
`1.0.0` major	Mar 28, 2021
`0.6.4` patch	Oct 27, 2020
`0.6.3` patch	Sep 08, 2020
`0.6.2` patch	Dec 20, 2019
`0.6.1` patch	Oct 04, 2019
`0.6.0` minor	Jul 29, 2019
`0.5.0` minor	Jan 18, 2019
`0.4.1` patch	Jun 11, 2018
`0.3.2` patch	Jun 11, 2018
`0.2.36` patch	Jun 11, 2018
`0.2.35` patch	Jun 06, 2018
`0.3.1` patch	Jun 06, 2018
`0.4.0` minor	Jun 06, 2018
`0.3.0` minor	Jun 05, 2018
`0.2.34` patch	Jun 05, 2018
`0.2.33` patch	Jun 05, 2018
`0.2.32` patch	Jun 05, 2018
`0.2.31` patch	May 22, 2018
`0.2.30` patch	May 18, 2018
`0.2.29` patch	Apr 20, 2018

3.1.0 minor

Jul 21, 2026

3.0.0 major yanked

1 CVE

RUSTSEC-2026-0218 Jul 21, 2026

`Enum` trait allows type confusion when manually implemented

Affected versions of this crate did not require the element type of the Array associated type in the Enum trait to match the array's generic parameter V.

This can result in type confusion, and consequently memory corruption, when a manual Enum implementation declares an Array<V> whose elements are not actually of type V:

struct IntentionallyWrong;

impl Enum for IntentionallyWrong {
    type Array<V> = [String; 4];

    fn from_usize(_: usize) -> Self {
        IntentionallyWrong
    }

    fn into_usize(self) -> usize {
        0
    }
}

enum_map! { IntentionallyWrong => 42 };

The flaw was corrected in commit 7a8b815432 by adding a Value = V bound to the Array type in the Enum trait.

Fixed in


          3.1.0

References

Updated Jul 28, 2026 · Source: OSV.dev

Jul 20, 2026

2.7.3 patch

Nov 24, 2023

2.7.2 patch yanked

Nov 16, 2023

3.0.0-beta.2 pre yanked

1 CVE

RUSTSEC-2026-0218 Jul 21, 2026

`Enum` trait allows type confusion when manually implemented

Affected versions of this crate did not require the element type of the Array associated type in the Enum trait to match the array's generic parameter V.

This can result in type confusion, and consequently memory corruption, when a manual Enum implementation declares an Array<V> whose elements are not actually of type V:

struct IntentionallyWrong;

impl Enum for IntentionallyWrong {
    type Array<V> = [String; 4];

    fn from_usize(_: usize) -> Self {
        IntentionallyWrong
    }

    fn into_usize(self) -> usize {
        0
    }
}

enum_map! { IntentionallyWrong => 42 };

The flaw was corrected in commit 7a8b815432 by adding a Value = V bound to the Array type in the Enum trait.

Fixed in


          3.1.0

References

Updated Jul 28, 2026 · Source: OSV.dev

Nov 08, 2023

2.7.1 patch

Nov 08, 2023

3.0.0-beta.1 pre yanked

1 CVE

RUSTSEC-2026-0218 Jul 21, 2026

`Enum` trait allows type confusion when manually implemented

Affected versions of this crate did not require the element type of the Array associated type in the Enum trait to match the array's generic parameter V.

This can result in type confusion, and consequently memory corruption, when a manual Enum implementation declares an Array<V> whose elements are not actually of type V:

struct IntentionallyWrong;

impl Enum for IntentionallyWrong {
    type Array<V> = [String; 4];

    fn from_usize(_: usize) -> Self {
        IntentionallyWrong
    }

    fn into_usize(self) -> usize {
        0
    }
}

enum_map! { IntentionallyWrong => 42 };

The flaw was corrected in commit 7a8b815432 by adding a Value = V bound to the Array type in the Enum trait.

Fixed in


          3.1.0

References

Updated Jul 28, 2026 · Source: OSV.dev

Oct 23, 2023

2.7.0 minor

Oct 20, 2023

3.0.0-0.gat.0 pre yanked

1 CVE

RUSTSEC-2026-0218 Jul 21, 2026

`Enum` trait allows type confusion when manually implemented

Affected versions of this crate did not require the element type of the Array associated type in the Enum trait to match the array's generic parameter V.

This can result in type confusion, and consequently memory corruption, when a manual Enum implementation declares an Array<V> whose elements are not actually of type V:

struct IntentionallyWrong;

impl Enum for IntentionallyWrong {
    type Array<V> = [String; 4];

    fn from_usize(_: usize) -> Self {
        IntentionallyWrong
    }

    fn into_usize(self) -> usize {
        0
    }
}

enum_map! { IntentionallyWrong => 42 };

The flaw was corrected in commit 7a8b815432 by adding a Value = V bound to the Array type in the Enum trait.

Fixed in


          3.1.0

References

Updated Jul 28, 2026 · Source: OSV.dev

Sep 23, 2023

2.6.3 patch

Sep 10, 2023

2.6.2 patch

Sep 07, 2023

2.6.1 patch

Aug 01, 2023

2.6.0 minor

Jun 30, 2023

2.5.0 minor

Mar 14, 2023

2.4.2 patch

Dec 17, 2022

2.4.1 patch

Jul 28, 2022

2.4.0 minor

Jun 15, 2022

2.3.0 minor

May 29, 2022

2.2.0 minor

May 20, 2022

2.1.0 minor

Mar 24, 2022

2.0.3 patch

Feb 26, 2022

0.6.6 patch

Feb 18, 2022

0.6.5 patch

Feb 18, 2022

2.0.2 patch

Feb 17, 2022

2.0.1 patch yanked

1 CVE

GHSA-rxhx-9fj6-6h2m RUSTSEC-2022-0010 Jun 16, 2022

enum_map macro can cause UB when `Enum` trait is incorrectly implemented

High

Affected versions of this crate did not properly check the length of an enum when using enum_map! macro, trusting user-provided length.

When the LENGTH in the Enum trait does not match the array length in the EnumArray trait, this can result in the initialization of the enum map with uninitialized types, which in turn can allow an attacker to execute arbitrary code.

This problem can only occur with a manual implementation of the Enum trait, it will never occur for enums that use #[derive(Enum)].

Example code that triggers this vulnerability looks like this:

enum E {
    A,
    B,
    C,
}

impl Enum for E {
    const LENGTH: usize = 2;

    fn from_usize(value: usize) -> E {
        match value {
            0 => E::A,
            1 => E::B,
            2 => E::C,
            _ => unimplemented!(),
        }
    }

    fn into_usize(self) -> usize {
        self as usize
    }
}

impl<V> EnumArray<V> for E {
    type Array = [V; 3];
}

let _map: EnumMap<E, String> = enum_map! { _ => "Hello, world!".into() };

The flaw was corrected in commit b824e23 by putting LENGTH property on sealed trait for macro to read.

Fixed in


          2.0.2

References

Updated Nov 08, 2023 · Source: OSV.dev

Jan 27, 2022

2.0.0 major yanked

1 CVE

GHSA-rxhx-9fj6-6h2m RUSTSEC-2022-0010 Jun 16, 2022

enum_map macro can cause UB when `Enum` trait is incorrectly implemented

High

Affected versions of this crate did not properly check the length of an enum when using enum_map! macro, trusting user-provided length.

When the LENGTH in the Enum trait does not match the array length in the EnumArray trait, this can result in the initialization of the enum map with uninitialized types, which in turn can allow an attacker to execute arbitrary code.

This problem can only occur with a manual implementation of the Enum trait, it will never occur for enums that use #[derive(Enum)].

Example code that triggers this vulnerability looks like this:

enum E {
    A,
    B,
    C,
}

impl Enum for E {
    const LENGTH: usize = 2;

    fn from_usize(value: usize) -> E {
        match value {
            0 => E::A,
            1 => E::B,
            2 => E::C,
            _ => unimplemented!(),
        }
    }

    fn into_usize(self) -> usize {
        self as usize
    }
}

impl<V> EnumArray<V> for E {
    type Array = [V; 3];
}

let _map: EnumMap<E, String> = enum_map! { _ => "Hello, world!".into() };

The flaw was corrected in commit b824e23 by putting LENGTH property on sealed trait for macro to read.

Fixed in


          2.0.2

References

Updated Nov 08, 2023 · Source: OSV.dev

Jan 10, 2022

2.0.0-2 pre yanked

1 CVE

GHSA-rxhx-9fj6-6h2m RUSTSEC-2022-0010 Jun 16, 2022

enum_map macro can cause UB when `Enum` trait is incorrectly implemented

High

Affected versions of this crate did not properly check the length of an enum when using enum_map! macro, trusting user-provided length.

When the LENGTH in the Enum trait does not match the array length in the EnumArray trait, this can result in the initialization of the enum map with uninitialized types, which in turn can allow an attacker to execute arbitrary code.

This problem can only occur with a manual implementation of the Enum trait, it will never occur for enums that use #[derive(Enum)].

Example code that triggers this vulnerability looks like this:

enum E {
    A,
    B,
    C,
}

impl Enum for E {
    const LENGTH: usize = 2;

    fn from_usize(value: usize) -> E {
        match value {
            0 => E::A,
            1 => E::B,
            2 => E::C,
            _ => unimplemented!(),
        }
    }

    fn into_usize(self) -> usize {
        self as usize
    }
}

impl<V> EnumArray<V> for E {
    type Array = [V; 3];
}

let _map: EnumMap<E, String> = enum_map! { _ => "Hello, world!".into() };

The flaw was corrected in commit b824e23 by putting LENGTH property on sealed trait for macro to read.

Fixed in


          2.0.2

References

Updated Nov 08, 2023 · Source: OSV.dev

Jan 04, 2022

2.0.0-1 pre

Oct 01, 2021

1.1.1 patch

May 16, 2021

1.1.0 minor

May 04, 2021

1.0.0 major

Mar 28, 2021

0.6.4 patch

Oct 27, 2020

0.6.3 patch

Sep 08, 2020

0.6.2 patch

Dec 20, 2019

0.6.1 patch

Oct 04, 2019

0.6.0 minor

Jul 29, 2019

0.5.0 minor

Jan 18, 2019

0.4.1 patch

Jun 11, 2018

0.3.2 patch

Jun 11, 2018

0.2.36 patch

Jun 11, 2018

0.2.35 patch

Jun 06, 2018

0.3.1 patch

Jun 06, 2018

0.4.0 minor

Jun 06, 2018

0.3.0 minor

Jun 05, 2018

0.2.34 patch

Jun 05, 2018

0.2.33 patch

Jun 05, 2018

0.2.32 patch

Jun 05, 2018

0.2.31 patch

May 22, 2018

0.2.30 patch

May 18, 2018

0.2.29 patch

Apr 20, 2018

Activity

Details