WhatBrokeToday
GTA 6FAQ
Ruby

Ruby Object-Document Mapper Fails to Encrypt Inherited Data Model Fields

high

Is it fixed? Not yet.

Ongoing since Nov 13, 16:18 UTC. First reported Nov 13, 16:18 UTC.

What happened

A high severity vulnerability in a Ruby object-document mapper causes it to fail to apply automatic field-level encryption configurations to certain fields when data models use class inheritance. Consequently, designated confidential values are written to the database in plaintext without warning, exposing them to database users lacking access to the encryption key store.

What caused it?

The object-document mapper does not apply automatic field-level encryption configuration to certain fields when the data model utilizes class inheritance.

No verified workaround yet

None of the linked reports describe a mitigation. This page updates when one appears.

Official fix

Timeline

  1. Investigating(current)
  2. Workaround available(upcoming)
  3. Resolved(upcoming)
  1. First report on security advisory

    A Ruby object-document mapper: CVE-2026-126818 (High)

    Source

Evidence

1 report · 1 CVEShow
  1. [1]
    CVE First report
    A Ruby object-document mapper: CVE-2026-126818 (High)(opens security advisory in a new tab)

    High severity. A Ruby object-document mapper does not apply its automatic field-level encryption configuration to certain fields when the data model uses class inheritance. Values the application designated for encryption are written to the database in readable form without any error or warning. A database account holding only read access to the application's collections, and no access to the encryption key store, may obtain those values.

    by Tenable 0upvotes 0comments

FAQ

What happened in the Ruby issue?

A high severity vulnerability in a Ruby object-document mapper causes it to fail to apply automatic field-level encryption configurations to certain fields when data models use class inheritance. Consequently, designated confidential values are written to the database in plaintext without warning, exposing them to database users lacking access to the encryption key store.

What is affected by the Ruby issue?

Ruby.

When did the Ruby issue start and end?

It started Nov 13, 16:18 UTC and is still ongoing (5 d 12 h so far). This page updates as it develops.

How do I get alerts for Ruby?

Subscribe to the Ruby RSS feed for every new Ruby incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether Ruby is down. Ruby feed

Where does this information come from?

WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 1 report from 1 independent source.