MAS 9.1.18 Lands: What's New in the May 2026 Feature Channel Release

Category: MAS Platform & Upgrades
Slug: mas-912-may-release-updates
Tags: MAS 9.1, Feature Channel, OpenShift, MAS Core, Upgrade, Release Notes, watsonx
Read Time: 10 min
Audience: Platform administrators, solution architects, upgrade planners
Summary:
IBM dropped MAS 9.1.18 on May 27, bringing cumulative fixes and platform hardening across the suite. This article breaks down what shipped, what changed, and how to plan your upgrade path.
The release coincides with continued MAS 9.2 Feature Channel momentum and a critical Manage security fix — so there's plenty to unpack.

The Release at a Glance

On May 27, 2026, IBM shipped MAS Core 9.1.18 alongside parallel updates for the 9.0 stream (9.0.26) and a wave of component patches. This release follows the now-familiar monthly cadence — but it lands with more heft than a typical point release, thanks to synchronized updates across Manage, Monitor, Health, Predict, IoT, AI Service, and Real Estate and Facilities.

Here's what landed on May 27:

What's Inside 9.1.18

IBM's release notes don't always itemize every change, but here's what we know from the documentation references and community signals:

Platform Hardening

The 9.1.17 release was reserved for internal use, making 9.1.18 the effective external update from 9.1.16 (April). This suggests the engineering team needed an intermediate build to address issues discovered post-April — a pattern we've seen before with the 9.1.11-9.1.15 reserved range. The result for customers: 9.1.18 rolls up fixes that otherwise would have shipped in 9.1.17.

Manage 9.1.18: Security-Patch Context

On May 29 — two days after the release — IBM published a security bulletin covering Manage versions 9.0.0+ and 9.1.0+. The remediation path is explicit:
- MAS 9.0.x → upgrade to Manage 9.0.26 or latest
- MAS 9.1.x → upgrade to Manage 9.1.18 or latest

If you're on any Manage version prior to these, this isn't optional reading. The bulletin follows IBM's standard vulnerability disclosure process and affects both SaaS and client-managed deployments.

AI Service 9.1.15: Platform Improvements

AI Service 9.1.15 shipped with two documented changes:
1. Security fix: Applied security improvements to the codebase
2. RSL Secret migration: Transitioned RSL Secret management from Ansible-based automation to operator-based implementation

That second item matters for operators. Moving secret management from Ansible to the operator pattern simplifies lifecycle management — fewer external scripts, more declarative control. If you're running Ansible playbooks that touch RSL secrets, review this before upgrading.

MAS 9.2 Feature Channel: Quiet but Steady

While the 9.1 stream gets the point-release treatment, MAS 9.2 continues on the Feature Channel model. The April 2026 Feature Channel shipped on April 30 with updates across the entire suite — Core, Manage, Monitor/IoT, Predict, AI Service, and Optimizer. The March and February channels preceded it like clockwork.

This dual-stream strategy — 9.1 point releases for stability, 9.2 Feature Channels for innovation — is now well-established. Organizations on 9.1 get predictable monthly patches. Those on 9.2 get continuous feature delivery.

Upgrade Planning: What You Need to Know

Path Selection

Your upgrade path depends on where you are today:

Pre-Upgrade Checklist

# 1. Verify current versions
oc get subscription -n mas-<instance>-core
oc get csv -n mas-<instance>-core

# 2. Check Operator Lifecycle Manager status
oc get clusterserviceversion -n mas-<instance>-core

# 3. Back up Suite CR
oc get suite <suite-name> -n mas-<instance>-core -o yaml > suite-backup.yaml

# 4. Review deprecated APIs
oc get apirequestcounts | grep -E "REMOVED|DEPRECATED"

Catalog Version Tagging

The May 27 release introduced updated catalog tags. For Maximo IT patch 9.0.45 (which shipped the same day), the catalog version is V9-260527-AMD64. Similar date-stamped tags apply to MAS Core and component channels. Always verify the catalog tag against your target release before initiating an upgrade.

What's Ahead: MAS 9.2 Maturation

MAS 9.2 is now on its eleventh Feature Channel release (counting from September 2025). Key capabilities that have matured across the FC stream:

• Condition Insight & AI-driven APM: Connecting Monitor → Health → Predict → Manage workflows
• Configurable dashboards: Role-based APM views
• Maximo Mobile expansion: Inspections, inventory, QR codes, crew management
• Geospatial improvements: Geofencing, linear asset visualization, 3D views
• Platform updates: OpenShift 4.19 support, MongoDB 8.0 compatibility
• SAP/Oracle integration enhancements: Cloud-based connectors

Organizations still evaluating MAS 9.2 should consider that the Feature Channel delivery model means you adopt capabilities incrementally rather than through a big-bang upgrade. This reduces risk but requires operational discipline around channel subscription management.

Community Signal

Maximo World 2026 (August 17-20, Nashville) will likely feature MAS 9.2 deep-dives and migration case studies. MaximoLive 2026 (October 14-15, Melbourne) promises community-driven content including customer migration stories. If you're planning a major version jump, both events offer invaluable peer learning.

The Bottom Line

MAS 9.1.18 is a maintenance release with teeth — the Manage security fix alone makes it a priority update. If you're on 9.1, schedule the upgrade. If you're on 9.2 FC, keep your channel subscriptions current. And if you're still on 8.x: the clock is ticking. IBM's investment is clearly in the MAS platform, and the 8.x sustainment window won't last forever.

Sources: IBM Support (MAS Releases Information, May 2026); IBM Security Bulletin (May 29, 2026); AI Service 9.1.15 Release Notes; Naviam MAS 9.2 Analysis (May 2026); Maximo IT Patch 9.0.45 Documentation